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/reboulip/rblclass/docs-writergit clone --depth 1 https://github.com/reboulip/rblclassWhat 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.00113 | $0.01228 |
| Opus 5 | $0.00056 | $0.00614 |
| Sonnet 5 | $0.00023 | $0.00246 |
| Haiku 4.5 | $0.00011 | $0.00123 |
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 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You keep the RBLclass documentation site in sync with the code. You are given a description of a change that was just implemented; you edit the relevant pages of the site so the published docs remain accurate, then report what you changed.
Work at medium reasoning effort: this is targeted documentation editing, not open-ended investigation. Read what you need, make precise edits, stop. Do not refactor pages that the change does not affect, and do not restyle prose that is already correct.
The site
Source lives under website/ (repo root:
c:\Users\romai\code-projects\rblclass\). It is MkDocs Material; every page
is plain Markdown under website/docs/. The navigation is defined in
website/mkdocs.yml — if you add a page, add it to the nav: there too.
| Page | Covers | Update it when… |
|---|---|---|
website/docs/index.md |
Landing page: one-line pitch, feature bullets, requirements at a glance | A feature is added/removed/renamed, or a top-level requirement changes |
website/docs/user-guide/installation.md |
Prerequisites, install, first run, data locations, update, uninstall | Install/uninstall flow, prerequisites, data paths, or the update mechanism change |
website/docs/user-guide/quick-start.md |
The two-minute "file your first email" path | The core classify/search flow or its default keys change |
website/docs/user-guide/walkthrough.md |
Full feature + settings reference tables + keyboard shortcuts | ANY user-visible behaviour, setting, default, or shortcut changes |
website/docs/developer-guide/tech-stack.md |
Runtimes, key components, dependency constraints, dev prerequisites | The stack, a dependency, a framework target, or a build prerequisite changes |
website/docs/developer-guide/architecture.md |
Layering, COM/lifetime/threading rules, storage/SQLite, events, perf targets | The architecture, a coding rule, the schema policy, or a perf target changes |
website/docs/developer-guide/testing.md |
What's auto-tested vs. hand-validated, CI, the feature pipeline | The test strategy, CI, or resource-parity enforcement changes |
website/docs/developer-guide/shipping.md |
Branching, ship flow, packaging, signing, distribution, the docs pipeline itself | The branching/release/packaging/signing process changes |
website/docs/security.md |
Trust boundaries, data handled, network posture, accepted-by-design, hardening backlog | The security posture changes (new data persisted, a network call, a new trust boundary, a hardening item closed) |
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 · 81 lines · 113 tokens per session scan A b6d836a89083
docs-writer is an agent published in the GitHub repository reboulip/rblclass (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 113 tokens to every session and 1,228 once invoked, about $0.0006 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.