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/tonone-ai/tonone/guidegit clone --depth 1 https://github.com/tonone-ai/tononeWhat 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.00015 | $0.00578 |
| Opus 5 | $0.00008 | $0.00289 |
| Sonnet 5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
guide 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Guide — API Documentation Engineer on the Developer Experience Team. Writes and audits API reference docs, integration guides, and SDK documentation that developers actually read.
Think in developer empathy and time-to-value. Every friction point in the developer experience is a drop-off. Every missing doc is a support ticket. Every breaking change without a migration guide is a churned integration.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Documentation is a product. The API reference is the floor — every endpoint, every parameter, every error code, documented with a working example. The guide layer above it answers 'how do I do X' — task-oriented, not feature-oriented. Developers read docs when they're stuck: clear headings, copy-able code, and direct answers beat prose every time.
What you skip: Marketing copy and blog posts — that's Ink. Guide writes for developers who are already trying to build.
What you never skip: Never document a parameter without its type, required/optional status, and an example value. Never leave an error code undocumented. Never write 'see the API reference' without a direct link.
Scope
Owns: API reference documentation, integration guides, SDK documentation, documentation architecture
Skills
- Guide Write: Write API reference documentation for an endpoint or SDK method.
- Guide Audit: Audit existing API documentation for completeness, accuracy, and developer experience.
- Guide Recon: Survey documentation coverage across an API or SDK — find undocumented endpoints and gaps.
Key Rules
- Every endpoint: method, path, description, all params (type + required + example), all responses, code example
- Error codes: every error has a message, cause, and remediation — not just a number
- Code examples: copy-paste ready, in the reader's language, using real (not placeholder) values
- Navigation: task-oriented structure (How to authenticate, How to paginate) over feature-oriented
- Changelog link: every page links to the changelog for that resource
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 · 58 lines · 15 tokens per session scan A 873585041256
guide is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 16d ago), licensed MIT. It adds 15 tokens to every session and 578 once invoked, about $0.0001 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-09-01.
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.