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/smart-ai-memory/empathy-framework/docsgit clone --depth 1 https://github.com/Smart-AI-Memory/empathy-frameworkWhat 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.00014 | $0.01779 |
| Opus 5 | $0.00007 | $0.00890 |
| Sonnet 5 | $0.00003 | $0.00356 |
| Haiku 4.5 | $0.00001 | $0.00178 |
Grade A, and why
docs 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation
Aliases: /documentation
Documentation operations powered by Socratic agents that help you understand and explain code.
Quick Examples
/docs # Interactive menu
/docs explain # Get code explanation with context
/docs generate # Generate documentation
/docs overview # Feature or module overview
/docs seo # SEO audit for documentation site
Discovery
Question:
header: "Task"
question: "What documentation task do you need?"
options:
- label: "Explain code"
description: "Understand how code works with guided exploration"
- label: "Generate docs"
description: "Create documentation for code or features"
- label: "Feature overview"
description: "High-level overview for stakeholders"
- label: "Optimize SEO"
description: "Audit and optimize documentation site SEO"
Explain Code
Agent: architect | Workflow: (code exploration)
Understand code through guided exploration, not just reading.
Invoke:
/docs explain # Interactive selection
/docs explain src/auth/oauth.py # Explain specific file
/docs explain "how does caching work" # Explain by concept
The architect agent will:
- Ask what you're trying to understand
- Explore the code structure together
- Guide you through the logic step by step
- Ask: "What do you think this function does based on its name?"
- Connect patterns to broader concepts
- Answer follow-up questions
Philosophy: Instead of "This function authenticates users", you'll hear "Looking at the function name and parameters, what do you think it does? Let's trace through what happens when a user logs in."
Good for:
- Onboarding to unfamiliar code
- Understanding complex algorithms
- Learning patterns used in codebase
- Preparing to make changes
Generate Documentation
Agent: architect | Workflow: document_gen
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 · 281 lines · 14 tokens per session scan A 5267e3429ad0
docs is a command published in the GitHub repository Smart-AI-Memory/empathy-framework (13 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,779 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-30.
Other commands, from other repositories
explain
Explain code or concepts clearly with practical examples and analogies.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
github-status
Check GitHub sync status for SpecWeave increment. Shows issue number, sync state, progress, last update, and any sync issues. Useful for troubleshooting and monitoring.