Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hainamchung/agent-assistantnpx agentmods add commands/hainamchung/agent-assistant/docsWrote 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/hainamchung/agent-assistant/docs)<a href="https://agentmods.dev/commands/hainamchung/agent-assistant/docs"><img src="https://agentmods.dev/badge/commands/hainamchung/agent-assistant/docs/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/hainamchung/agent-assistant/docs"><img src="https://agentmods.dev/badge/commands/hainamchung/agent-assistant/docs.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.00017 | $0.01828 |
| Opus 5.5 | $0.00007 | $0.00731 |
| Sonnet 5.5 | $0.00003 | $0.00366 |
| Haiku 4.5 | $0.00002 | $0.00183 |
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 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/docs — Full Documentation Suite
MISSION: Execute ALL documentation sub-commands SEQUENTIALLY. Only report "Done" when ALL deliverables are created: 5 knowledge folders (26+ files) + 4 business folders (22+ files) + 4 audit folders (20+ files).
$ARGUMENTS
🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
LOAD now (in order; path ./rules/ or ~/.{TOOL}/skills/agent-assistant/rules/):
- CORE.md — Identity, Laws, Routing
- PHASES.md — Phase Execution
- AGENTS.md — Tiered Execution
⛔ Do not run any workflow phase until all are loaded. Follow all rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant (e.g. docs/core.md), and execute it.
⚠️ EXECUTION RULES (NON-NEGOTIABLE)
[!CAUTION]
- You MUST execute each sub-command IN ORDER
- You MUST wait for each sub-command to COMPLETE before starting next
- You MUST create ALL deliverables across 3 sub-commands
- You may NOT skip any sub-command
- Report "Done" ONLY when all deliverables exist
🔄 SEQUENTIAL EXECUTION FLOW
┌─────────────────────────────────────────────────────────────────┐
│ STEP 1: Load & Execute /docs:core │
│ → Wait until ALL 5 knowledge folders are created │
│ → Each folder: 00-index.md + numbered sub-files │
│ → Verify: knowledge-overview/, architecture/, domain/, │
│ → source-base/, standards/ │
├─────────────────────────────────────────────────────────────────┤
│ STEP 2: Load & Execute /docs:business │
│ → Wait until ALL 4 business folders are created │
│ → Verify: business-prd/, features/, workflows/, glossary/ │
├─────────────────────────────────────────────────────────────────┤
│ STEP 3: Load & Execute /docs:audit │
│ → Wait until ALL 4 audit folders are created │
│ → Verify: audit-security, compliance, dataflow, │
│ recommendations │
└─────────────────────────────────────────────────────────────────┘
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 · 180 lines · 17 tokens per session scan A 55239c74c5b0
docs is a command published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 1,828 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
anchors
List what each requirement tag anchors to (read-only).
review
Review proposed ADRs for lifecycle progression — accept implemented decisions, deprecate stale ones, archive trivial ones.
from-spec
Extract Architecture Decision Records from a completed spec.
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
docs-refresh
Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.
spec-forge
Use when generating software specifications — full chain ([Idea]→[Decompose]→[PRD]→SRS→Tech Design→Review) or individual documents.