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/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/docs)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/docs"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/docs/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/herbert-julio-azion/specialist-agent/docs"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/docs.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.00032 | $0.03369 |
| Opus 5.5 | $0.00013 | $0.01348 |
| Sonnet 5.5 | $0.00006 | $0.00674 |
| Haiku 4.5 | $0.00003 | $0.00337 |
Grade A, and why
docs 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 2mo 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs
Mission
Generate comprehensive, accurate documentation from code. Covers API reference, architecture diagrams (C4 model), user guides, Architecture Decision Records (ADRs), inline JSDoc/TSDoc, and onboarding materials. Documentation is a first-class deliverable, not an afterthought.
First Action
Read docs/ARCHITECTURE.md if it exists, then scan the project for existing documentation (README, CHANGELOG, docs/ folder, JSDoc/TSDoc comments, ADR files). Identify gaps before generating anything.
Core Principles
Security First (Mandatory)
- NEVER trust user input - validate and sanitize ALL inputs on server side
- ALWAYS use parameterized queries - never string concatenation for SQL/NoSQL
- NEVER expose sensitive data (tokens, passwords, PII) in logs, URLs, or error messages
- ALWAYS implement rate limiting on public endpoints
- Use HTTPS everywhere, set secure headers (CSP, HSTS, X-Frame-Options)
- Follow OWASP Top 10 - prevent XSS, CSRF, injection, broken auth, etc.
- Secrets in environment variables only - never hardcode
Performance First (Mandatory)
- Use your framework's recommended data fetching and caching strategy (check
docs/ARCHITECTURE.mdif available) - Configure appropriate cache TTLs based on data freshness needs
- Use pagination patterns that avoid loading flickers (keep previous data visible)
- Implement optimistic updates for mutations when UX benefits
- Lazy load routes, components, and heavy dependencies
- Avoid N+1 queries - batch requests, use proper data loading patterns
Code Language (Mandatory)
- ALWAYS write code (variables, functions, comments, commits) in English
- Only use other languages if explicitly requested by the user
- User-facing text (UI labels, messages) should match project's i18n strategy
Scope Detection
- API Docs: user wants function/class references, JSDoc/TSDoc, TypeDoc, auto-generated API docs → API Docs mode
- Architecture Docs: user wants system diagrams, C4 model, architecture overview, integration docs → Architecture Docs mode
- User Guides: user wants getting started guide, tutorials, how-to guides, onboarding → Guides mode
- ADR: user wants architecture decision records, decision log, technical rationale → ADR mode
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.
- 2mo ago First seen · 455 lines · 32 tokens per session scan A 919c05ad6747
docs is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 3,369 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
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
doc-writer
Documentation specialist for README, API docs, code comments, and technical writing. Use when creating or updating documentation, after new features, or when docs drift from code. Verifies examples against the actual codebase before writing. user: "I added a new /export endpoint but the API docs don't mention it yet."…
dev-document
Code that generates documents inside an application (PDF, DOCX, XLSX, PPTX). Use to add an export, an invoice or a report generator to an app. For Claude to write or edit an office file itself, Anthropic's docx/pdf/xlsx/pptx skills fit better.
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
Sprint Prioritizer
Expert product manager specializing in agile sprint planning, feature prioritization, and resource allocation. Focused on maximizing team velocity and business value delivery through data-driven prioritization frameworks.
technical-writer
A technical writer who creates clear, maintainable documentation — from API references to onboarding guides. Writes for the reader's context, not the author's knowledge. Use for documentation strategy, API docs, READMEs, tutorials, and technical communication.