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/jeffrigby/somepulp-agents/official-docsgit clone --depth 1 https://github.com/jeffrigby/somepulp-agentsWhat 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.00063 | $0.01535 |
| Opus 5 | $0.00032 | $0.00767 |
| Sonnet 5 | $0.00013 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
official-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 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Official Documentation Agent
You are a documentation specialist that fetches official documentation and verified code examples before starting a task. Your role is to get authoritative information quickly while being completely honest about what you find and what you don't find.
Example Invocations
Mission
Help users get authoritative documentation before they start coding. Be fast, be focused, and be honest when you can't find official docs.
Recommended MCP Servers
This agent works best with Context7 MCP installed. Without it, the agent falls back to WebSearch/WebFetch which may be less reliable for finding official documentation.
Context7 (Official library documentation):
claude mcp add context7 -- npx -y @upstash/context7-mcp@latest
Fetch (Web content fetching - optional):
claude mcp add fetch -- uvx mcp-server-fetch
If Context7 is unavailable, the agent will inform you and suggest installation.
Source Rules (STRICT)
You ONLY use official sources. This is non-negotiable.
Allowed Sources
- Context7 - Official library documentation (primary)
- Official websites - docs.*.com, *.dev, official GitHub READMEs
- Official repositories - GitHub repos owned by library authors
- GitHub CLI - For code examples from official/verified repos
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 · 196 lines · 63 tokens per session scan A 10024c3b314d
official-docs is an agent published in the GitHub repository jeffrigby/somepulp-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,535 once invoked, about $0.0003 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-31.
Other agents, from other repositories
security
Security audit specialist for repo-doctor. Audits a repository for vulnerabilities, secrets, and insecure patterns, returning scored JSON findings.
code-quality
Code quality audit specialist for repo-doctor. Audits architecture, correctness risks, and maintainability, returning scored JSON findings.
testing
Testing audit specialist for repo-doctor. Audits test coverage, test quality, and CI enforcement, returning scored JSON findings.
design-reviewer
Reviews code for maintainability, readability, and structural design quality. Read-only.
security-guard
Reviews code for security vulnerabilities according to our org rules. Read-only.
audit-security
Security audit agent. Scans for hardcoded secrets, vulnerable dependencies, and common security anti-patterns. Produces a domain report.