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/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/wtfp-check-refs)<a href="https://agentmods.dev/commands/akougkas/wtf-p/wtfp-check-refs"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-check-refs/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/akougkas/wtf-p/wtfp-check-refs"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-check-refs.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.00028 | $0.00141 |
| Opus 5 | $0.00014 | $0.00071 |
| Sonnet 5 | $0.00006 | $0.00028 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
wtfp: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 10d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- check-refs — 97% identical, 3 lines differ
- wtfp:request-feature — 86% identical, 12 lines differ
What it actually says
WTFP_ACTION_UNAVAILABLE
Action: check-refs
Target: antigravity
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.
- 10d ago First seen · 18 lines · 28 tokens per session scan A 45c13add49d9
wtfp:check-refs is a command published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 11d ago), licensed MIT. It adds 28 tokens to every session and 141 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-30.
Other commands, from other repositories
retro
Reflect on the current research session and collect improvement suggestions.
setup_research_plan
Set up or start a research project.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.