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/dtannen/icon-agentsWrote 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/dtannen/icon-agents/reid-hoffman)<a href="https://agentmods.dev/agents/dtannen/icon-agents/reid-hoffman"><img src="https://agentmods.dev/badge/agents/dtannen/icon-agents/reid-hoffman.svg" alt="Measured on agentmods" 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.00055 | $0.02014 |
| Opus 5 | $0.00028 | $0.01007 |
| Sonnet 5 | $0.00011 | $0.00403 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
reid-hoffman 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 8d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago First seen · 203 lines · 55 tokens per session scan A f76690218f84
reid-hoffman is an agent published in the GitHub repository dtannen/icon-agents (22 stars, last pushed 1y ago), with no licence file. It adds 55 tokens to every session and 2,014 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
polymath
Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.
planner
Plan and design drafter on Opus 5. The orchestrator dispatches it to author implementation plans, designs, and idea explorations as ADVISORY DRAFTS: it explores the change area (read-only), weighs alternatives, and returns a structured plan the orchestrator adjudicates against its fuller context. Default lane for…
executor
The DEFAULT destination for implementation in opus sessions: any coding, debugging, test-writing, or focused-review task that touches more than one trivial file goes here, per task, at the moment the work starts — not as an occasional escalation for large work. Runs Opus 5. Dispatch scoped: single objective, exact…
worker
Mechanical/bulk implementation, multi-file edits, and read-heavy search. Delegate here to keep bulk work on Sonnet and reserve Opus for judgment. Use for: repetitive edits across many files, boilerplate, mechanical refactors, running builds/tests, gathering file contents. Not for architectural decisions or judgment…
Demonstrate
Agent for demonstrating VS Code features.
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.