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/thrashr888/agentkernel/secretsgit clone --depth 1 https://github.com/thrashr888/agentkernelWhat 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 | $0.00000 | $0.00445 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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 yesterday.
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.
What it actually says
agentkernel secret
Manage secrets (API keys and credentials) in the secret vault.
Subcommands
| Command | Description |
|---|---|
secret set <KEY> [VALUE] |
Store a secret (reads from stdin if value not provided) |
secret get <KEY> |
Retrieve a secret value |
secret list |
List all stored secret keys |
secret delete <KEY> |
Delete a secret |
Examples
Store a secret
# Set directly
agentkernel secret set ANTHROPIC_API_KEY sk-ant-...
# Read from stdin (more secure, avoids shell history)
echo "sk-ant-..." | agentkernel secret set ANTHROPIC_API_KEY
Retrieve a secret
agentkernel secret get ANTHROPIC_API_KEY
List secrets
$ agentkernel secret list
Keys:
ANTHROPIC_API_KEY
OPENAI_API_KEY
GITHUB_TOKEN
Delete a secret
agentkernel secret delete GITHUB_TOKEN
Storage Backends
The vault supports three backends, configured in agentkernel.toml:
[secrets]
backend = "file" # "file" (default), "env", or "keyring"
| Backend | Storage | set/delete | Best For |
|---|---|---|---|
file |
~/.agentkernel/secrets.json (base64-encoded, 0600 perms) |
Yes | Local development |
env |
Host environment variables | No (read-only) | CI/CD pipelines |
keyring |
OS keychain (macOS Keychain, Linux secret-service) | Yes | Production workstations |
The keyring backend requires building with the keyring Cargo feature.
See Also
- Secrets Overview — proxy injection, placeholder tokens, file injection, SDK usage, and security model
- Agents — agent-specific API key configuration
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.
- yesterday First seen · 70 lines · 0 tokens per session scan A 3911c7ee10ce
secrets is a command published in the GitHub repository thrashr888/agentkernel (58 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 445 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-08-30.
Other commands, from other repositories
diagnose
Run sivtr doctor to check the environment, then investigate any failing checks.
test-changed
Run the full quality gate on only the files changed since branching from main.
test_mcp
Test all rust-docs-testing tools found in @rust-docs-mcp/src/service.rs.
update_mcp_tools_list
Read the rust-docs-mcp/src/service.rs module and ensure that the README.md and the rust-docs-mcp/install.sh files have up to date lists of the tools available in the MCP.
review
You are an expert code reviewer. Your job is to review code changes and provide actionable feedback.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.