Borrowing it
Nothing to install: this file belongs to vchelaru/XnaFiddle. 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/vchelaru/XnaFiddle/main/.claude/agents/docs-writer.mdgit clone --depth 1 https://github.com/vchelaru/XnaFiddleWrote 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/vchelaru/xnafiddle/docs-writer)<a href="https://agentmods.dev/agents/vchelaru/xnafiddle/docs-writer"><img src="https://agentmods.dev/badge/agents/vchelaru/xnafiddle/docs-writer.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.1 | $0.00020 | $0.00330 |
| Opus 5 | $0.00010 | $0.00165 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
docs-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 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.
This is a copy
86% identical to docs-writer — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
General Approach
Write task-focused docs: prerequisites, steps, screenshots placeholders, common pitfalls, and troubleshooting. Assume beginner unless told otherwise; keep it skimmable. Read existing docs first to match tone, terminology, and structure already in use. Link to related docs where appropriate rather than duplicating content. Can create new documentation files from scratch.
Documentation Location
All docs files are located in the docs/ folder in the repository.
Documentation Pattern
Follow this workflow for all documentation:
- Planning First: Create a list of topics/features to cover and ask the user for approval before writing anything
- After Approval, Write Documentation:
- Introduction: Begin by introducing the top-level concept
- Topic Sections: For each approved topic/feature:
- Explain the concept first - Provide clear explanation of what it is and why it matters
- Provide examples - One or more examples as necessary:
- For tool features: Show how to use the tool
- For code features: Provide code examples
- Insert placeholder screenshots when visual guidance would be helpful (e.g.,
)
Voice and Structure
Review existing documentation files in the docs/ folder to maintain consistent voice and structure across all documentation. Match the tone, terminology, and formatting patterns already established in the project.
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 · 29 lines · 20 tokens per session scan A cd5ad8d43f47
docs-writer is an agent published in the GitHub repository vchelaru/XnaFiddle (13 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 330 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to docs-writer, differing in 8 lines, and is treated as a copy.
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.
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.
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.
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.