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/subcog/namespacesgit clone --depth 1 https://github.com/zircote/subcogWhat 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.00757 |
| Opus 5 | $0.00003 | $0.00378 |
| Sonnet 5 | $0.00001 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
namespaces 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/subcog:namespaces
Display all available memory namespaces with descriptions and usage guidance.
Usage
/subcog:namespaces
Execution Strategy
Namespaces Reference
Choosing the Right Namespace
- Is this a choice we made? →
decisions - Is this a recurring practice? →
patterns - Did I just discover something? →
learnings - Is this background info? →
context - Is this something to fix later? →
tech-debt - Is this about an API? →
apis - Is this about settings? →
config - Is this security-related? →
security - Is this about speed? →
performance - Is this about testing? →
testing
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 · 91 lines · 6 tokens per session scan A ac196cf09b0c
namespaces is a command published in the GitHub repository zircote/subcog (28 stars, last pushed 29d ago), licensed MIT. It adds 6 tokens to every session and 757 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-30.
Other commands, from other repositories
setup
kb MCP 연결 점검·재설정 안내 — 설치 직후 연결 확인, 서버 URL/토큰 변경, 연결 실패 진단에 사용.
version
Display current guide and Claude Code versions.
index
Index the codebase for semantic search.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
codesage-reindex
Force an incremental codesage re-index (use when git hooks didn't fire). Auto-cleans orphan vec tables if the config model has changed.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.