Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/gotempsh/temps/secretsgit clone --depth 1 https://github.com/gotempsh/tempsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/gotempsh/temps/secrets)<a href="https://agentmods.dev/commands/gotempsh/temps/secrets"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/secrets.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
secrets scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
secrets command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
secrets (alias: secret)
Manage agent secrets. env-type: reference as ${TEMPS_SECRET:name} in MCP config. file-type: written to --mount-path in sandbox; reference that path.
Subcommands:
list(ls) - List all secrets (values are masked)create(add) - Create or update a secret (upsert by name)update- Update an existing secret (alias for create — upserts)delete(rm) - Delete a secret
secrets list (alias: ls)
List all secrets (values are masked)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
secrets create (alias: add)
Create or update a secret (upsert by name)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-n, --name <name> |
Secret name | - | Yes |
-v, --value <value> |
Secret value. Prefix with @ to read from file (e.g. @./creds.json) | - | Yes |
-t, --type <type> |
Secret type: "env" (default) or "file" | env |
No |
-m, --mount-path <path> |
Absolute path inside sandbox where file-type secret is written (required for --type file) | - | No |
-d, --description <description> |
Human-readable description | - | No |
secrets update
Update an existing secret (alias for create — upserts)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-n, --name <name> |
Secret name | - | Yes |
-v, --value <value> |
New value. Prefix with @ to read from file | - | No |
-t, --type <type> |
Secret type: "env" or "file" | - | No |
-m, --mount-path <path> |
New mount path (file type only) | - | No |
-d, --description <description> |
New description | - | No |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 66 lines · 0 tokens per session scan A e9b5164e9a52
secrets is a command published in the GitHub repository gotempsh/temps (712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 642 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
pr-check
Run all local CI checks before creating a PR.
ci-health
Check all GitHub Actions workflows for failures, create P0 tickets, gate each ticket, and auto-fix safe failures.
ci-status
Real-time GitHub Actions workflow status and recent runs.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.