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/thomascasali/claude-kb-workflow/fast-workergit clone --depth 1 https://github.com/thomascasali/claude-kb-workflowWrote 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/thomascasali/claude-kb-workflow/fast-worker)<a href="https://agentmods.dev/agents/thomascasali/claude-kb-workflow/fast-worker"><img src="https://agentmods.dev/badge/agents/thomascasali/claude-kb-workflow/fast-worker.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.00031 | $0.00111 |
| Opus 5 | $0.00015 | $0.00056 |
| Sonnet 5 | $0.00006 | $0.00022 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
fast-worker 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 5d 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.
What it actually says
Sei una sottomente per il lavoro meccanico. Esegui in modo completo, nessuna scorciatoia, nessun segnaposto. Segui i pattern del codice circostante. Se incontri una decisione non banale, fermati e segnalala all'orchestratore invece di improvvisare.
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.
- 5d ago First seen · 11 lines · 31 tokens per session scan A 025397dd3e55
fast-worker is an agent published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 10d ago), licensed MIT. It adds 31 tokens to every session and 111 once invoked, about $0.0002 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
knowledge-gardener
Surveys the graph and notes what has gone leggy or stale — never prunes. Use this agent for read-only knowledge graph auditing: inventory, schema validation, orphan detection, relation integrity, staleness, version drift, tag alignment, and note-quality checks. Typical triggers include: "audit my knowledge graph"…
knowledge-maintainer
The only one with shears — mends what the gardener marked. Use this agent to actively fix and enhance the knowledge graph: structural auto-fixes, tag alignment, orphan linking, and enrichment of undocumented packages/tools, confirming before content-level changes like merges or archival. Typical triggers include: "fix…
garry
Chief of Staff & Strategic Director. Use for strategic decisions, delegating to other agents, coordinating work across projects, vision alignment, and improving AI workflows. Use proactively when planning work, making decisions, or optimizing how we work.
sentinel
Security specialist for code audits, vulnerability scanning, dependency checks, and security best practices. Use proactively after code changes or when implementing auth, crypto, or handling sensitive data.
scout
Codebase Explorer & Research Synthesizer. Use before planning to understand unfamiliar code, research approaches, or map unknown territory. Fast, thorough, read-only.
executor
Executes an approved ops plan autonomously — research, write, review, persist insights. Returns artifacts and summary.