Borrowing it
Nothing to install: this file belongs to jamesaoyama/fugu-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jamesaoyama/fugu-mcp/main/.claude/commands/fugu.mdgit clone --depth 1 https://github.com/jamesaoyama/fugu-mcpWrote 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/jamesaoyama/fugu-mcp/fugu)<a href="https://agentmods.dev/commands/jamesaoyama/fugu-mcp/fugu"><img src="https://agentmods.dev/badge/commands/jamesaoyama/fugu-mcp/fugu/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/jamesaoyama/fugu-mcp/fugu"><img src="https://agentmods.dev/badge/commands/jamesaoyama/fugu-mcp/fugu.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.00024 | $0.00255 |
| Opus 5 | $0.00012 | $0.00128 |
| Sonnet 5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
fugu 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.
What it actually says
Use the ask_fugu tool (provided by the fugu MCP server) to get a
second opinion from the Sakana Fugu orchestration model.
Send this as the tool's prompt argument, verbatim:
$ARGUMENTS
Guidance:
ask_fuguis for hard, self-contained subproblems where a second, independent model's perspective is valuable (cross-checking an approach, an isolated reasoning/algorithm question, a tricky design tradeoff).- It is not for interactive, iterative repo work — Fugu has no access to
this repo or conversation context; pass everything it needs inside
prompt. - If
$ARGUMENTSis empty, ask me what I'd like to send to Fugu before calling the tool. - After the tool returns, summarize Fugu's answer and note where it agrees or disagrees with your own view (treat it as one voice in a panel, not ground truth).
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 · 24 lines · 24 tokens per session scan A daee0896ee65
fugu is a command published in the GitHub repository jamesaoyama/fugu-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 255 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 commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.