Part
Secrets
You might say: scoped credentials, runtime tokens, protected variables
Credentials made available to a run through a controlled scope. The runner receives only the values and permissions the task needs.
- What it does
- Lets a run authenticate to required services while reducing the value of a stolen workspace or log.
- Ask
- Which credential reaches this run, for how long, and can its value or authority leave the boundary?
- Typical
- Use repository, environment, or organization scopes. Prefer short-lived tokens and OIDC where the target supports it. A proxy can add the value to outgoing requests, so the agent uses the credential without seeing it.
- Trouble
- A secret is available to an untrusted change, appears in output, persists on disk, or grants more API access than the task needs.
What to look for
- A named secret reference in the run configuration
- A masked value in logs and a permissions scope
- An OIDC or short-lived token exchange
Connections
- See also: Prompt injection
- See also: Network egress
Sources
- GitHub, Using secrets in GitHub Actions, Using secrets in a workflow
With the exception of `GITHUB_TOKEN`, secrets are not passed to the runner when a workflow is triggered from a forked repository.
- GitHub, Using secrets in GitHub Actions, Using secrets in a workflow
To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository.
- OpenAI, OpenAI-hosted sandboxes, Set environment variables
For secrets, use vault credentials to keep the real values outside the sandbox.
- Kody, Documentation, Credentials
Code names a credential. Kody puts the value into the outgoing request at the network boundary, only for the hosts that credential allows, and only over HTTPS. Agents, packages, logs, and tool output never see it.
- Kent C. Dodds, You Own the Outcome: Product Engineering in the Age of AI, Design the playground
Agents should be able to use credentials without ever seeing them. This is non-negotiable once agents are acting on your behalf.
Use it on your project
teardown-apply: hold "Secrets" (secrets) from the teardown at https://teardownatlas.com/software-factory/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal