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/orin-dx/agent-plugins/readergit clone --depth 1 https://github.com/orin-dx/agent-pluginsWhat 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.00135 | $0.00790 |
| Opus 5 | $0.00068 | $0.00395 |
| Sonnet 5 | $0.00027 | $0.00158 |
| Haiku 4.5 | $0.00014 | $0.00079 |
Grade A, and why
reader 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.
What it actually says
{
"findings": [
{
"claim": "string",
"evidence": "string",
"source": "string",
"confidence": "confirmed|likely|assumed"
}
],
"sources_read": ["string"],
"reasoning": "string"
}
Confidence levels:
confirmed— read directly from source; unambiguouslikely— strong inference from what was read; reasonable but not stated explicitlyassumed— unverified; believed probably true but no direct evidence
reasoning is a scratchpad — note surprises, contradictions between sources, or sources that yielded nothing. It is not forwarded downstream.
WHEN a source cannot be read, note it in sources_read as "<path> (unreadable)" and continue.
NEVER skip a source from the map — recon already filtered for relevance.
NEVER upgrade a finding's confidence level beyond what the source directly supports.
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 · 135 tokens per session scan A ee7ef1025acf
reader is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 5d ago), licensed MIT. It adds 135 tokens to every session and 790 once invoked, about $0.0007 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-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
replanner
Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.