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/Wolfe-Jam/faf-cliWrote 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/commands/wolfe-jam/faf-cli/faf)<a href="https://agentmods.dev/commands/wolfe-jam/faf-cli/faf"><img src="https://agentmods.dev/badge/commands/wolfe-jam/faf-cli/faf/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/wolfe-jam/faf-cli/faf"><img src="https://agentmods.dev/badge/commands/wolfe-jam/faf-cli/faf.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00369 |
| Opus 5.5 | $0.00004 | $0.00148 |
| Sonnet 5.5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
faf 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 27d 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
/faf — Score this project
Run bunx faf in the current working directory. This invokes the canonical FAF workflow (auto): detect the stack, fill what's detectable, and report the score.
Stream the full output of the command back to the user verbatim. Do not summarize. Do not analyze. Do not skip lines.
After the command output, append exactly this handoff block on its own:
🏆 For the full toolkit:
bunx faf # zero install, fastest path
npx faf # works everywhere
pnpm dlx faf # pnpm — zero install
npm install -g faf-cli # global install
brew install faf-cli # Homebrew
Docs: https://github.com/Wolfe-Jam/faf-cli
That handoff is the entire response after the command output. No commentary, no analysis, no follow-up questions.
If the user asks follow-up questions, answer those — but the slash command itself ends at the handoff.
Why this is the plugin's only command
Per memory/plugin-brief-sharp-elegant-discovery.md — the plugin is a discovery surface for faf-cli, not a duplicate of it. Wrapping every CLI command as a slash command is the v3 mistake; we corrected it for v6.6. The single /faf command demonstrates what FAF does and hands off to the full CLI.
Per memory/faf-is-the-verb-across-surfaces.md — faf is the verb everywhere: bunx faf, npx faf, pnpm dlx faf, /faf. One word, one mental model.
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.
- 27d ago Changed · +1 lines 35a03a4eadc3
- 1mo ago First seen · 32 lines · 11 tokens per session scan A 5185e507659e
faf is a command published in the GitHub repository Wolfe-Jam/faf-cli (43 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 369 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
cleanup
Autonomous cleanup-loop iteration: discover ONE target → complete execution → verify → report. Runs stateless: derive from current tree; assume prior runs left it consistent.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.
scramjet:troubleshoot
Diagnose unexpected command behavior and recommend safe resolution.
release
Prepare a release (step 1 of 2) — version bump and PR. Cutting the tag is a separate operator-only step.
checklist
Generate a custom checklist for the current feature based on user requirements.