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/audit-loggit 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.00006 | $0.02110 |
| Opus 5 | $0.00003 | $0.01055 |
| Sonnet 5 | $0.00001 | $0.00422 |
| Haiku 4.5 | $0.00001 | $0.00211 |
Grade A, and why
audit-log 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 — 276 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>
AUDIT-LOG(1) User Commands AUDIT-LOG(1)
NAME
audit-log - View the secrets filtering audit log
SYNOPSIS
/memory:audit-log [OPTIONS]
DESCRIPTION
View the audit log of secrets filtering operations. The audit log records
all detections, filtering actions, and allowlist changes for compliance.
OPTIONS
--since <time> Show entries after this time (e.g., "1h", "24h", "7d")
--namespace <ns> Filter to specific namespace
--type <type> Filter by event type: detection, filter, scan, allowlist
--json Output in JSON format (one entry per line)
--limit <n> Maximum entries to show (default: 50)
--help, -h Show this help message
TIME FORMATS
Relative: 1h (1 hour), 24h (24 hours), 7d (7 days), 30d (30 days)
Absolute: 2024-01-15 or 2024-01-15T10:30:00
EXAMPLES
/memory:audit-log
Show recent audit entries (last 50)
/memory:audit-log --since 24h
Show entries from the last 24 hours
/memory:audit-log --type detection --limit 100
Show last 100 detection events
/memory:audit-log --namespace decisions --json
JSON output for decisions namespace
/memory:audit-log --type allowlist
Show allowlist changes only
SEE ALSO
/memory:scan-secrets - Scan memories for secrets
/memory:secrets-allowlist - Manage allowlist
AUDIT-LOG(1)
</help_output>
After outputting help, HALT immediately. Do not proceed with command execution. </help_check>
/memory:audit-log - View Secrets Audit Log
View the audit log of secrets filtering operations for compliance and debugging.
Your Task
You will query and display the audit log based on the provided filters.
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 · 276 lines · 6 tokens per session scan A fd351bad0c84
audit-log is a command published in the GitHub repository zircote/git-notes-memory (4 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 2,110 once invoked, about $0.0000 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.