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/fakoli/fakoli-plugins/fakoli-smithgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/fakoli-smith)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/fakoli-smith"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/fakoli-smith.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 | $0.00026 | $0.00138 |
| Opus 5 | $0.00013 | $0.00069 |
| Sonnet 5 | $0.00005 | $0.00028 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
fakoli-smith 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 4d 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
You are the Cursor companion for the Fakoli Crew smith subagent.
When available, read plugins/fakoli-crew/agents/smith.md and follow that canonical prompt as the source of truth.
Own plugin internals: manifests, commands, hooks, agent frontmatter, path resolution, and plugin-local version sync.
Keep plugin changes schema-compliant, portable, and minimal. Route repository-wide infrastructure concerns to keeper.
Write status files only when the orchestrator gives you an explicit path.
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.
- 4d ago First seen · 13 lines · 26 tokens per session scan A fa9b7578e20e
fakoli-smith is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 26d ago), licensed MIT. It adds 26 tokens to every session and 138 once invoked, about $0.0001 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
audit-ecosystem
Audits MCP servers, plugins, and hooks against expert knowledge. Dispatched by /claudit during Phase 2.
research-plugin-spec
Researches Claude Code plugin, skill, and sub-agent authoring from official Anthropic documentation. Shared by /smith and /hone.
research-ecosystem
Researches Claude Code ecosystem from official Anthropic documentation. Dispatched by /claudit during Phase 1. Builds expert knowledge on MCP, plugins, hooks, skills, and subagents.
spec-scout
Use this agent at the START of every /kana-spec engagement on an existing codebase (skip only for true greenfield) to map what exists for the subject being specified. Spawn it BEFORE framing or interviewing — its cited map pre-fills the interview and grounds every later claim. For large repos (>200 source files) or…
tech-lead
Orchestrate development work — understand the task, surface unknowns, route by size to the right executors, gate quality with an independent review, and close with a summary.
verification-agent
Run the project's deterministic checks — build, typecheck, lint, tests, security scan — and report exactly what ran and what it said, ending in a machine-parseable verdict.