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 commands/akougkas/wtf-p/check-refsgit clone --depth 1 https://github.com/akougkas/wtf-pWrote 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/akougkas/wtf-p/check-refs)<a href="https://agentmods.dev/commands/akougkas/wtf-p/check-refs"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/check-refs.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.00021 | $0.00130 |
| Opus 5 | $0.00010 | $0.00065 |
| Sonnet 5 | $0.00004 | $0.00026 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
check-refs 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.
This is a copy
97% identical to wtfp:check-refs — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
WTFP_ACTION_UNAVAILABLE
Action: check-refs
Target: claude
Unavailable capabilities: tool.execute
Unavailable effects: tool.execute
No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran. Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
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 · 17 lines · 21 tokens per session scan A 34b30783ec06
check-refs is a command published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 130 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to wtfp:check-refs, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
fd-execute
Implement plan.md with the TDD pipeline — parallel worktree guard from affect.md, wave-based execution, checkpoint after each wave.
fd-done
Close the task — summarize built vs required, then commit and push on confirmation.
fd-review
Two-lens review of the task artifacts before execution — CEO review challenges scope and premise, eng review checks architecture, edge cases, and blast radius.
fd-verify
Verify the implementation — run tests, check regression on affect.md files, review and scan; blocks /fd-done on failure.
fd-resume
Restore from checkpoint.json (falling back to STATE.md) — brief the user, PAUSE for confirmation, then continue from the recorded command and stage.
fd-checkpoint
Purpose: Force-save the current session to checkpoint.json and STATE.md so it can be safely resumed later with /fd-resume. Normally runs automatically on session.idle via the session-events hook; invoke manually to force a save before closing a session.