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.
git clone --depth 1 https://github.com/vinilana/dotcontextWrote 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/vinilana/dotcontext/documentation-writer)<a href="https://agentmods.dev/agents/vinilana/dotcontext/documentation-writer"><img src="https://agentmods.dev/badge/agents/vinilana/dotcontext/documentation-writer/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/vinilana/dotcontext/documentation-writer"><img src="https://agentmods.dev/badge/agents/vinilana/dotcontext/documentation-writer.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.00009 | $0.01403 |
| Opus 5.5 | $0.00004 | $0.00561 |
| Sonnet 5.5 | $0.00002 | $0.00281 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
documentation-writer 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer
Role
Create and maintain documentation for the dotcontext project, both the user-facing README/guides and the internal .context/ documentation that the tool itself generates. This includes writing doc templates, improving scaffold structures, updating the guide registry, and ensuring documentation accurately reflects the current CLI commands and service capabilities.
Key Files to Understand
README.md-- Project README, the primary user-facing documentation. Covers installation, CLI usage, commands, and configuration..context/docs/README.md-- Index of generated documentation within the.context/directory structure..context/agents/README.md-- Index of agent playbooks.src/generators/documentation/documentationGenerator.ts-- Core generator that scaffolds documentation files in.context/docs/. Creates files for project overview, architecture, API reference, testing, onboarding, etc.src/generators/documentation/guideRegistry.ts-- Registry of all documentation guide types (DOCUMENT_GUIDES). Each guide has a name, description, category, and template. Adding new documentation types starts here.src/generators/documentation/templates/-- Template functions that produce the initial content for each documentation type. Containscommon.ts(shared template helpers),indexTemplate.ts(README index), and type definitions.src/generators/shared/structures/documentation/-- Scaffold structure definitions for each doc type:projectOverview.ts,architecture.ts,apiReference.ts,testing.ts,onboarding.ts,workflow.ts,security.ts,tooling.ts,glossary.ts,troubleshooting.ts,migration.ts,dataFlow.ts.src/services/ai/tools/fillScaffoldingTool.ts-- MCP scaffold-fill helpers. Understanding the context returned here is essential for writing templates that produce good output in connected AI tools.src/services/autoFill/autoFillService.ts-- Static auto-fill layer used during scaffold generation. Good structures improve both auto-filled starter content and MCP-guided completion.src/utils/i18n.ts-- Translation system. Documentation-related UI strings (section headers, progress messages) must be translatable.
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 · 56 lines · 9 tokens per session scan A c7a231f4ca26
documentation-writer is an agent published in the GitHub repository vinilana/dotcontext (573 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 1,403 once invoked, about $0.0000 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.