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/zircote/git-notes-memory/test-secretgit clone --depth 1 https://github.com/zircote/git-notes-memoryWhat 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.00010 | $0.01421 |
| Opus 5 | $0.00005 | $0.00711 |
| Sonnet 5 | $0.00002 | $0.00284 |
| Haiku 4.5 | $0.00001 | $0.00142 |
Grade A, and why
test-secret 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<help_check>
Help Check
If $ARGUMENTS contains --help or -h:
Output this help and HALT (do not proceed further):
<help_output>
TEST-SECRET(1) User Commands TEST-SECRET(1)
NAME
test-secret - Test if a value would be detected as a secret
SYNOPSIS
/memory:test-secret <value>
DESCRIPTION
Test if a given value would be detected as a secret by the filtering system.
Shows the detection type, confidence score, and what filtering strategy would apply.
This is useful for:
- Verifying detection rules work correctly
- Understanding why content was blocked/redacted
- Testing before adding to allowlist
OPTIONS
--help, -h Show this help message
EXAMPLES
/memory:test-secret "AKIAIOSFODNN7EXAMPLE"
Test if this looks like an AWS access key
/memory:test-secret "123-45-6789"
Test if this looks like a US SSN
/memory:test-secret "4111111111111111"
Test if this looks like a credit card number
/memory:test-secret "sk-proj-abc123xyz"
Test if this looks like an OpenAI API key
NOTES
The value is not stored anywhere - this is purely for testing.
Use quotes around values containing spaces or special characters.
SEE ALSO
/memory:scan-secrets - Scan memories for secrets
/memory:secrets-allowlist - Manage allowlist
TEST-SECRET(1)
</help_output>
After outputting help, HALT immediately. Do not proceed with command execution. </help_check>
/memory:test-secret - Test Secret Detection
Test if a value would be detected as a secret by the filtering system.
Your Task
You will analyze a value and report whether it would be detected as a secret.
Arguments format: $ARGUMENTS
The entire argument is the value to test. Handle quoted strings.
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 · 197 lines · 10 tokens per session scan A 86135c0eaf93
test-secret is a command published in the GitHub repository zircote/git-notes-memory (4 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 1,421 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
memory-graph
Open the memory graph visualization in your browser.
memory-recall
Turn this project's automatic memory recall off or back on (storing stays active).
memory-status
Show a memory health digest for this project (items, sessions, injections served).
assets
Inventory .claude-design/ / — file counts, types, locations.
start
Run the canvas-to-code workflow — guided discovery, auto-resume, or jump to a specific gate.
dashboard
Work timeline — what's done, what's in progress, when, with PR + doc links.