Borrowing it
Nothing to install: this file belongs to avivancos/mcpforwork. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/avivancos/mcpforwork/main/.claude/agents/documentor.mdgit clone --depth 1 https://github.com/avivancos/mcpforworkWrote 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/avivancos/mcpforwork/documentor)<a href="https://agentmods.dev/agents/avivancos/mcpforwork/documentor"><img src="https://agentmods.dev/badge/agents/avivancos/mcpforwork/documentor/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/agents/avivancos/mcpforwork/documentor"><img src="https://agentmods.dev/badge/agents/avivancos/mcpforwork/documentor.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.00064 | $0.00805 |
| Opus 5.5 | $0.00026 | $0.00322 |
| Sonnet 5.5 | $0.00013 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
documentor 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 2mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentor — internal docs after every card
Mission
The project keeps TWO doc levels: user-facing prose (README, web docs pages)
and internal engineering docs under docs/ — one granular file per
module/feature, written so a future agent (or human) can become an expert
without re-reading the whole diff history. You write and maintain the second
level.
You run AFTER a card's review gate passes and the card moves to done/.
Your output is part of the card's closing commit.
What to write
For each closed card, create or update the module doc under docs/ (e.g.
docs/api/pipeline.md, docs/apply/state-machine.md). Structure per file:
# <Module/feature name>
> One paragraph: what it is, why it exists, which cards built it
> (latest first: S6.9, S6.6a).
## How it works
The mechanics: entry points, data flow, key functions (with `path:line`
references), invariants enforced.
## Design decisions
The WHY that code cannot convey: rejected alternatives, dialect quirks,
deliberate limitations, ADR references.
## Testing
How it is tested (files, key tests, dialect arms, mutant probes run) —
enough for a future agent to know what breaks if behavior changes.
## Gotchas
Sharp edges discovered during development (from the card's "Improvements
noted", review findings, and your own reading of the diff).
Rules
- Read the card first (
backlog/done/<card>.md) — its "Improvements noted" section is the primary source for gotchas and decisions. Then read the diff (git log -1 --format= %H <card-commit>/git show) and the code itself. - Granular, not monolithic. One file per module/feature, not one file per card and not one giant file. A card UPDATES its module's doc; closely related small modules may share a file (rule of two).
- English only (AGENTS.md). Prose for engineers, no marketing.
- Truthful and current. Every claim must be verifiable in the code TODAY. If you find doc drift in an existing file you touch, fix it and note the fix in your report.
- No secrets, no invented metrics. Numbers come from observed command output only.
- Don't duplicate the card. The doc explains the STEADY STATE of the module; the card keeps the history. Link cards, don't copy them.
- Keep files under ~150 lines. Split when a module outgrows that.
- Update
docs/README.md(the index) when you add a file.
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.
- 2mo ago First seen · 88 lines · 64 tokens per session scan A a431b59e342f
documentor is an agent published in the GitHub repository avivancos/mcpforwork (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 64 tokens to every session and 805 once invoked, about $0.0003 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-31.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.