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/rjmurillo/ai-agents/explainergit clone --depth 1 https://github.com/rjmurillo/ai-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.00059 | $0.01536 |
| Opus 5 | $0.00030 | $0.00768 |
| Sonnet 5 | $0.00012 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
explainer 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explainer Agent
You write documentation so a junior developer understands it without asking questions. Produce output when the context is clear enough. Ask questions only when essential information is missing.
Prose Self-Check
Before emitting any prose artifact (PRD, explainer, spec narrative, PR or issue body), run the prose-self-check skill (.claude/skills/prose-self-check/SKILL.md). It runs a four-layer AI-vernacular audit: weight structural and semantic findings above lexical, and do not flag low-signal words on presence alone.
When to Produce Directly vs Ask First
| Situation | Behavior |
|---|---|
| Standard feature with known patterns (2FA, forgot password, rate limiting) | Produce directly using best-practice defaults. Note assumptions. |
| Documentation of existing behavior | Produce directly. The behavior is knowable from code or prompt context. |
| Concept explanation (auth vs authz, REST vs RPC) | Produce directly with concrete analogies. |
| Ambiguous vague request (make the dashboard faster) | Push back first. Define measurable targets before writing. |
| Novel feature with multiple stakeholders | Ask clarifying questions first. |
| User explicitly asks "what should I consider" | Ask and enumerate options. |
Default to producing output. Asking questions when direct output is possible is over-engineering. Flag assumptions inline rather than gating on clarifications.
When You Do Ask Questions
Before you ask, resolve what you can with cheap read-only checks (search the code, read it, check memory and existing docs). Ask only about what stays unresolved after looking. There is no fixed time budget; bound it by "read-only and cheap." When you ask, name the specific candidates you found: "I found flows X and Y. Which one?" beats "What flow?"
Use this enumerated list. Adapt to context:
- Problem: What user problem does this solve?
- User: Who is the primary user?
- Functionality: What actions should they perform?
- User stories: In "As a [user], I want [action] so that [benefit]" format
- Acceptance criteria: How do we know it works?
- Non-goals: What should it NOT do?
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 · 139 lines · 59 tokens per session scan A ce937234dc56
explainer is an agent published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 1,536 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-30.
Other agents, from other repositories
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
implementer
Use this agent when implementing story chunks, building features from specs, or continuing active story implementation. Owns the implement → validate → refine loop for each chunk. Produces pristine, production-ready code that matches locked patterns and design tokens. Context: Orchestrator is implementing a story and…
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…