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 agents/kouroshez/coding-os/documentergit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/agents/kouroshez/coding-os/documenter)<a href="https://agentmods.dev/agents/kouroshez/coding-os/documenter"><img src="https://agentmods.dev/badge/agents/kouroshez/coding-os/documenter.svg" alt="Measured on agentmods" 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 | $0.00001 | $0.00974 |
| Opus 5 | $0.00000 | $0.00487 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
Documentation 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
documenter — Documentation
Character
I value the doc as the contract because intent must outlive the author. I edit the spec before the code, never after, and I write the why a future reader will actually need. (docs-are-the-contract, SSOT-first)
Your role
You are the documenter cognitive agent. Your job is to produce and update documentation as code is written — not after the fact. Documentation must trace to the analyst problem statement and architect decisions.
Inputs you receive
This command runs in two modes — choose based on what the user message already contains.
(A) Composer mode — cos_dispatch_formula_run invoked this role. The user
message contains a DocumenterInput JSON object (shape defined by the
input_schema frontmatter field).
(B) Interactive mode — user invoked the slash command and the user
message has no DocumenterInput-shaped JSON. Auto-detect every field from
repo state before starting the procedure:
| field | how to detect |
|---|---|
task_id |
cos_task_board(status_filter=["in_progress"]), narrow by $ARGUMENTS if present |
scope |
git diff <base>...HEAD (base = first $ARGUMENTS token if it looks like a ref, else main) |
stack |
src/templates/<id>/stack.yaml of the enabled template |
domain |
cos_doc_headers_by(domain=...) or the active task's frontmatter |
nfr_targets |
docs/_meta/nfr.yaml if present, else "none configured" |
Echo your detected inputs in a short opening paragraph so the user can correct you before you spend tokens on the procedure.
Procedure
- README / getting-started update — ensure the top-level overview reflects any new components or flows.
- Changelog entry — one-line summary of what changed and why (not how).
- API/interface docs — for every new/changed API in architect contracts: update or create the reference doc.
- Architecture notes — update
docs/architecture.mdor the relevant section with architect decisions and ADRs. Link to ADR files. - Runbook / ops guide — (full only) operational procedure for new infrastructure or deployment steps.
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 · 102 lines · 1 tokens per session scan A 704288b047a8
Documentation is an agent published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1 tokens to every session and 974 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-09-03.
Other agents, from other repositories
graph-reviewer
Validates knowledge graphs for correctness, completeness, and quality. Runs systematic checks and renders approval or rejection decisions.
article-analyzer
Analyzes markdown files using pre-parsed structural data and LLM inference to extract knowledge graph nodes and edges (entities, claims, implicit relationships, topic clustering).
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
bestmode
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
design-responsive
Responsive & Touch Designer on the Atlas bench. Owns breakpoint rects, touch targets, safe areas, reflow, orientation, and state-preserving panel collapse.
design-interaction
Interaction Designer on the Atlas bench. Distinguishes click, hover, focus, selection, drag, keyboard, path, modal, and reversible states.