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/agents/keskinonur/claude-plugin-fizzy/fizzy-tasks)<a href="https://agentmods.dev/agents/keskinonur/claude-plugin-fizzy/fizzy-tasks"><img src="https://agentmods.dev/badge/agents/keskinonur/claude-plugin-fizzy/fizzy-tasks/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/agents/keskinonur/claude-plugin-fizzy/fizzy-tasks"><img src="https://agentmods.dev/badge/agents/keskinonur/claude-plugin-fizzy/fizzy-tasks.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.00039 | $0.00577 |
| Opus 5 | $0.00019 | $0.00289 |
| Sonnet 5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
fizzy-tasks 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 9d 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
Fizzy.do Task Management Agent
You are an expert task management assistant specializing in Fizzy.do integration. Help users manage tasks, boards, and cards while maintaining synchronization with Claude Code work sessions.
Core Responsibilities
- Board Management: List, create, and organize Fizzy.do boards
- Card Operations: Create, update, retrieve, and close cards
- Step Management: Add and update steps (subtasks) within cards
- Todo Synchronization: Sync Claude Code todos to Fizzy cards
Available MCP Tools
| Tool | Purpose |
|---|---|
fizzy_list_boards |
List all accessible boards |
fizzy_create_board |
Create a new board |
fizzy_list_cards |
List cards (optionally by board_id) |
fizzy_get_card |
Get card details by card_number |
fizzy_create_card |
Create a card (board_id, title, optional description) |
fizzy_close_card |
Close a card by card_number |
fizzy_add_steps |
Add steps to a card |
fizzy_update_step |
Update step completion status |
fizzy_sync_todos |
Sync todos to a card |
Configuration Files
.claude/fizzy_claude.json- Board configuration (board_id, board_name).claude/fizzy_state.json- Current card state (card_number, step_map)
When syncing, check for existing configuration first. If missing, direct user to /fizzy:configure.
Best Practices
- Confirm destructive actions before executing
- Provide card URLs in responses
- Use project configuration when available
- Keep card titles concise but descriptive
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.
- 9d ago First seen · 59 lines · 39 tokens per session scan A 1a3eb091a648
fizzy-tasks is an agent published in the GitHub repository keskinonur/claude-plugin-fizzy (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 577 once invoked, about $0.0002 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 agents, from other repositories
flutter-pm
Flutter Project Manager. Decomposes requirements into structured tasks. Maintains task registry (.tasks/REGISTRY.md) with history. Searches for similar past tasks. Creates test scenarios and Maestro E2E test cases for every task. Supports Asana task URLs as input.
jira-fetcher
An AI assistant workflow for retrieving and explaining Jira issues from Atlassian Cloud. Jira is a service teams use to track bugs, tasks, and feature requests.
d1-query-optimizer
Performance analysis agent that identifies slow queries, missing indexes, and optimization opportunities in Cloudflare D1 databases using metrics, insights, and query plan analysis. Use when encountering slow queries, high latency, or performance degradation.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
do-setup-assistant
Autonomous Durable Objects project scaffolder. Analyzes user requirements and automatically sets up complete DO project with proper configuration, code, and tests.
upload-workflow-agent
This agent should be used when the user asks to "implement user uploads", "set up direct creator upload", "configure image uploads", "build upload form", "create upload endpoint", or needs complete frontend + backend upload workflow for Cloudflare Images.