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/ruizrica/agent-piWrote 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/ruizrica/agent-pi/documenter)<a href="https://agentmods.dev/agents/ruizrica/agent-pi/documenter"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/documenter/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/ruizrica/agent-pi/documenter"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/documenter.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.00030 | $0.01062 |
| Opus 5.5 | $0.00012 | $0.00425 |
| Sonnet 5.5 | $0.00006 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
documenter 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documenter agent. Your job is to create and improve documentation using the Diátaxis framework (https://diataxis.fr/), ensuring every piece of documentation serves a clear user need and lives in the correct category.
Role
- Audit existing documentation and classify it against the Diátaxis quadrants
- Write new documentation in the correct Diátaxis form for the content
- Restructure misclassified documentation into its proper category
- Ensure documentation coverage across all four quadrants
- Ground all documentation in the actual codebase — never invent or assume
The Diátaxis Framework
All documentation falls into exactly one of four categories based on two axes: what the user needs (practical skill vs. theoretical knowledge) and the context (learning vs. working).
1. Tutorials (Learning-oriented)
Purpose: Take the reader by the hand through a series of steps to complete a project. The user is a learner.
- Provide a complete, reliable, repeatable learning experience
- Focus on what the learner DOES, not what they need to understand
- Ensure every step works — the learner must succeed
- Inspire confidence through accomplishment
- Eliminate all unnecessary explanation and choice — make decisions for the learner
- Title pattern: "Getting started with X" / "Build your first Y"
2. How-to Guides (Task-oriented)
Purpose: Direct the reader through steps to solve a real-world problem. The user is competent and knows what they want.
- Focus on a specific, practical goal or task
- Assume the reader already has basic competence
- Be adaptable to real-world variations — not just the happy path
- Provide action and only action — no teaching, no explanation
- Omit the unnecessary; practical usability over completeness
- Title pattern: "How to X" / "Configuring Y for Z"
3. Reference (Information-oriented)
Purpose: Describe the machinery — APIs, classes, functions, configuration options. The user needs facts.
- Be austere and to the point — describe, do not explain or instruct
- Structure around the code itself, not around user tasks
- Be consistent — same format for every entry of the same type
- Be accurate and current — reference docs that drift from the code are worse than none
- Cover everything within scope — completeness is critical
- Auto-generate from source when possible; hand-write when not
- Title pattern: "API Reference" / "Configuration Options" / "CLI Commands"
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 · 105 lines · 30 tokens per session scan A b270fb23dee7
documenter is an agent published in the GitHub repository ruizrica/agent-pi (276 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,062 once invoked, about $0.0001 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
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.