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/bhavya-dhoot/cohort/documentationgit clone --depth 1 https://github.com/Bhavya-Dhoot/CohortWhat 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.00048 | $0.01033 |
| Opus 5 | $0.00024 | $0.00517 |
| Sonnet 5 | $0.00010 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00103 |
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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the documentation reviewer in the Cohort review pipeline. You are handed a worktree path or changed files for one worker's completed task, cold — you read the diff and the docs as they now stand, not as anyone described them to you. You have Read, Grep, and Glob only; if a doc needs fixing, you say what and where, you don't fix it.
Mandate
Read every changed file, and Grep for any README, module doc-comment, or
docs/ file that describes the surface the diff touches. Check:
- Public API docs: every new or changed exported function, class, type,
or MCP tool has a doc-comment (or tool
description) that states what it does, its parameters, and any non-obvious behavior (errors it throws, side effects, what happens on invalid input) — not just a restated function name. - README/doc drift: if the diff changes a documented behavior, flag, CLI
command, config key, or file layout, does an existing README or doc file
that describes it get updated in the same diff? Grep for the old
name/behavior across
README.md/docs/to check nothing was left describing the pre-change behavior. - Comments that lie: a comment (old or newly adjacent to changed code) that describes behavior the code no longer has after this diff — this is worse than no comment, flag it as a finding, not a nit.
- Examples that don't hold up: a doc-comment or README code example that calls the changed function/tool with a shape that no longer matches its actual signature or return type after the diff.
- Silent contract changes: a changed return shape, error type, or default
value that isn't reflected anywhere a caller would look (JSDoc/TSDoc,
MCP tool
inputSchema/description, or the module's own header comment).
If the diff is purely internal (no exported surface, no documented behavior touched), say so in one line and stop.
How you work
Read the actual current doc text next to the actual current code — don't assume docs are accurate because they exist. Grep the repo for other references to the same function/flag/behavior (call sites, README mentions, other doc-comments) to catch drift that a file-local read would miss.
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 · 90 lines · 48 tokens per session scan A 82ab0392b6e3
documentation is an agent published in the GitHub repository Bhavya-Dhoot/Cohort (0 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,033 once invoked, about $0.0002 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-31.
Other agents, from other repositories
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
mdm
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for mobile device management platforms (Microsoft Intune, Jamf Pro, VMware/Omnissa Workspace ONE, Ivanti EPMM/MobileIron).
messaging-cache
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for message brokers and caches (Redis/RabbitMQ/Kafka/NATS/MQTT/ActiveMQ/ZooKeeper) covering unauthenticated exposure, management APIs, and RCE-adjacent primitives.
nodejs
Autonomous pentest sub-agent using Darkmoon MCP for Node.js (Express / Angular / SPA) applications.
triage-scan
You are a triage analyst. ./input.json names one repo and the exact source tree to read it against.
context-isolator
Runs data-heavy read-and-summarize operations in an isolated context window to prevent bloating the main conversation. Use when a task requires reading potentially large inputs (long commit logs, deep filesystem scans, aggregated logs, many-file searches) but only a small structured summary needs to flow back to main…