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.
git clone --depth 1 https://github.com/zircote/subcogWrote 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/zircote/subcog/integrate)<a href="https://agentmods.dev/commands/zircote/subcog/integrate"><img src="https://agentmods.dev/badge/commands/zircote/subcog/integrate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/zircote/subcog/integrate"><img src="https://agentmods.dev/badge/commands/zircote/subcog/integrate.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.03536 |
| Opus 5.5 | $0.00005 | $0.01414 |
| Sonnet 5.5 | $0.00002 | $0.00707 |
| Haiku 4.5 | $0.00001 | $0.00354 |
Grade A, and why
integrate 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 1mo 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/subcog:integrate
Analyze, enhance, or create AI prompts, skills, commands, and configurations to leverage Subcog's persistent memory system effectively.
Usage
/subcog:integrate # Interactive mode (recommended)
/subcog:integrate --analyze # Analyze current project for integration opportunities
/subcog:integrate --enhance CLAUDE.md # Enhance specific file
/subcog:integrate --create skill # Create new memory-aware artifact
Interactive Workflow
Step 1: Discover Current State
- Check for existing Subcog integration:
- Read project
CLAUDE.mdif exists - Read
~/.claude/CLAUDE.mdif exists - Check for
hooks/hooks.jsonor.claude/hooks.json - Scan
skills/andcommands/directories
- Read project
- Call
subcog_statusto verify memory system is healthy - Call
subcog_recallwith query "subcog integration patterns" to surface existing guidance
Step 2: Ask What to Analyze/Enhance
Use AskUserQuestion to present options:
- CLAUDE.md / System Prompts
- Skills & Commands
- Hooks Configuration
- MCP Tool Usage Patterns
- All of the above (comprehensive audit)
Step 3: Perform Analysis
Based on selection, analyze artifacts and generate recommendations.
Step 4: Present Recommendations
Show a structured report with:
- Current state summary
- Missing integration points
- Specific recommendations with code snippets
- Priority ranking (high/medium/low impact)
Step 5: Offer to Apply Changes
Ask user which recommendations to apply, then make the changes.
Analysis Patterns
Check for:
- Subcog Memory Protocol section exists
-
subcog_initcall instruction at session start - Recall-before-implement pattern documented
- Capture-immediately guidance present
- MCP-only access pattern specified (no shell commands)
- Namespace guidance for the project domain
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.
- 1mo ago First seen · 475 lines · 12 tokens per session scan A 928781b33253
integrate is a command published in the GitHub repository zircote/subcog (29 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 3,536 once invoked, about $0.0000 per session on Opus 5.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
reflexion-analyze
Steps 1-3 of reflexion: Parse feedback, categorize root causes, store reflections, generate retry guidance.
ask-about-me
Ask a question about the user's personal profile via the mcp-me MCP server.
feature-discover
Phase 1.5 of develop: Informed discovery, disambiguation, 7-category questions, understanding document, devil's advocate.
crystallize-verify
Adversarial review of a crystallized document against its original. Use when crystallize.md invokes pre-delivery verification. Receives original + crystallized documents; returns PASS or FAIL with findings.
test-bar
Generate a floating QA test overlay for the current branch's UI changes. Use when user says /test-bar, needs visual QA scenarios, or wants to test conditional rendering paths.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.