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/keskinonur/claude-plugin-fizzyWrote 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/keskinonur/claude-plugin-fizzy/setup)<a href="https://agentmods.dev/commands/keskinonur/claude-plugin-fizzy/setup"><img src="https://agentmods.dev/badge/commands/keskinonur/claude-plugin-fizzy/setup.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.00006 | $0.00267 |
| Opus 5 | $0.00003 | $0.00133 |
| Sonnet 5 | $0.00001 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade B, and why
setup scanned grade B with 2 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 ~/.claude/plugins/fizzy/config.json Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Bearer TOKEN_HERE" -H "Accept: application/json" https://app.fizzy.do/my/identity | jq -r 'if .accounts[0].name then "✓ Connected: " + .accounts[0].name else "✗ Invalid token" end' What it actually says
Fizzy Setup
Connect the plugin to your Fizzy.do account.
Usage
/fizzy:setup <token> where token is from https://app.fizzy.do/settings
Steps
- Save the token securely:
mkdir -p ~/.claude/plugins/fizzy
echo '{"token": "TOKEN_HERE", "url": "https://app.fizzy.do"}' > ~/.claude/plugins/fizzy/config.json
chmod 600 ~/.claude/plugins/fizzy/config.json
- Verify the connection:
curl -s -H "Authorization: Bearer TOKEN_HERE" -H "Accept: application/json" https://app.fizzy.do/my/identity | jq -r 'if .accounts[0].name then "✓ Connected: " + .accounts[0].name else "✗ Invalid token" end'
-
On success, tell the user:
- Setup complete! Run
/fizzy:configure "Board Name"to set your sync target.
- Setup complete! Run
-
On failure, ask user to verify their token at https://app.fizzy.do/settings
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.
- 6d ago First seen · 35 lines · 6 tokens per session scan B df064e8426fb
setup is a command published in the GitHub repository keskinonur/claude-plugin-fizzy (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 267 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
cloudflare-durable-objects:debug
Interactive Durable Objects debugging workflow. Diagnoses common DO errors, configuration issues, and runtime problems with step-by-step troubleshooting.
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-images:validate-config
Validate wrangler.jsonc configuration, verify Cloudflare Images bindings, check environment variables, and test Workers integration. Ensures correct setup for using Cloudflare Images with Cloudflare Workers.
cloudflare-queues:setup
Interactive wizard to set up Cloudflare Queues with queue creation, producer/consumer binding configuration, and Dead Letter Queue setup. Use when user wants to create first queue or add queues to existing Worker.
cloudflare-workers:migrate
Platform migration assistant for moving applications from AWS Lambda, Vercel, Netlify, or Cloudflare Pages to Cloudflare Workers.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.