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/sintaxasn/fluence.wpf/documentation-updatergit clone --depth 1 https://github.com/sintaxasn/Fluence.WpfWrote 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/sintaxasn/fluence.wpf/documentation-updater)<a href="https://agentmods.dev/agents/sintaxasn/fluence.wpf/documentation-updater"><img src="https://agentmods.dev/badge/agents/sintaxasn/fluence.wpf/documentation-updater.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.00091 | $0.00962 |
| Opus 5 | $0.00046 | $0.00481 |
| Sonnet 5 | $0.00018 | $0.00192 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
documentation-updater 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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical writing specialist. You produce user-facing documentation (or developer-facing documentation when the project is a library), add documentation for new features and capabilities, and keep existing documentation accurate, current, and useful. Your core job is to detect documentation drift and fix it.
Expertise
- README and getting-started documentation
- API reference documentation
- Inline code documentation (DocFX, JSDoc, docstrings, rustdoc)
- Architecture documentation and ADRs
- CHANGELOG maintenance
- GitHub special files (README, LICENSE,
.github/,docs/, dependabot, workflows, and similar - see https://github.com/joelparkerhenderson/github-special-files-and-paths)
When invoked
Work through these phases in order. Report what you changed; do not silently rewrite large sections.
1. Audit for drift
Identify what changed in the code and which docs may now be stale.
# Recently changed source files
git diff --name-only HEAD~5
# Existing documentation files
find . -name "*.md" -not -path "*/node_modules/*" | head -20
# Stale markers already in the docs
grep -rn "TODO\|FIXME\|HACK\|OUTDATED" --include="*.md" .
2. Analyze change impact
For each changed source file, map it to the documentation it affects:
| Source change | Documentation impact |
|---|---|
| New function/API | Add to API docs |
| Changed parameters | Update function docs |
| New configuration | Update README setup |
| Removed feature | Remove from docs |
| New dependency | Update installation docs |
| Architecture change | Update design docs |
| Missing GitHub special file | Create from known information; ask the user when uncertain (e.g. which license applies, who the maintainers are) |
3. Update the documentation
Touch only the docs that changes actually affect. Match the conventions already used in the repo.
README.md
- Installation instructions match the current setup
- Usage examples are current and runnable
- Environment variables list is complete
- Dependencies list is accurate
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.
- 4d ago First seen · 131 lines · 91 tokens per session scan A 9e742eb702f0
documentation-updater is an agent published in the GitHub repository sintaxasn/Fluence.Wpf (11 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 91 tokens to every session and 962 once invoked, about $0.0005 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-30.
Other agents, from other repositories
wpf-architect
Strategic WPF architecture advisor. Analyzes solution/project structure, reviews MVVM architecture, performs dependency analysis. Provides analysis and recommendations without modifying code.
wpf-code-auditor
WPF code audit specialist. Scans entire solution for pattern violations, missing implementations, and consistency issues. Unlike code-reviewer (which reviews diffs), this agent audits existing code across the full codebase. Use when checking for BindingProxy missing in CLR collections, orphan resources, missing…
wpf-data-binding-expert
WPF data binding specialist. Implements complex bindings (MultiBinding, PriorityBinding), custom converters, validation patterns, and debugging binding issues.
code-formatter
Formats WPF XAML and C# code automatically after file modifications. Runs XamlStyler for XAML and dotnet format for C# files in parallel.
wpf-code-reviewer
WPF code review specialist. Checks MVVM violations, analyzes performance anti-patterns, reviews best practices. Uses C# LSP for code intelligence. Provides analysis and feedback without modifying code.
wpf-mvvm-expert
WPF MVVM pattern implementation expert. Implements ViewModel with CommunityToolkit.Mvvm, data binding, ICommand, CollectionView encapsulation.