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 skills add keskinonur/claude-plugin-fizzy --skill fizzy-workflowgit 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/skills/keskinonur/claude-plugin-fizzy/fizzy-workflow)<a href="https://agentmods.dev/skills/keskinonur/claude-plugin-fizzy/fizzy-workflow"><img src="https://agentmods.dev/badge/skills/keskinonur/claude-plugin-fizzy/fizzy-workflow/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/skills/keskinonur/claude-plugin-fizzy/fizzy-workflow"><img src="https://agentmods.dev/badge/skills/keskinonur/claude-plugin-fizzy/fizzy-workflow.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.00057 | $0.00388 |
| Opus 5 | $0.00028 | $0.00194 |
| Sonnet 5 | $0.00011 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
fizzy-workflow 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
Fizzy.do Guided Workflow Skill
Provides structured workflows for Fizzy.do task management. For direct operations, use the fizzy-tasks agent.
Workflows
Project Setup
Triggers: "set up Fizzy", "configure Fizzy for this project"
- Check
.claude/fizzy_claude.jsonfor existing config - Verify FIZZY_TOKEN is available
- List boards or create new one
- Save configuration
Sync Todos
Triggers: "sync my work", "sync todos to Fizzy"
- Verify board is configured
- Gather and summarize todos
- Confirm card title
- Execute
fizzy_sync_todos
Progress Review
Triggers: "review my progress", "show Fizzy status"
- Load board config
- Fetch and categorize cards
- Present summary with step counts
Session Cleanup
Triggers: "end of session", "wrap up"
- Review current card from state
- Confirm completion status
- Close card if appropriate
Configuration
| File | Contents |
|---|---|
.claude/fizzy_claude.json |
board_id, board_name |
.claude/fizzy_state.json |
card_number, card_title, step_map |
Related
- Agent:
fizzy-tasks- Direct operations - Commands:
/fizzy:configure,/fizzy:status
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 57 tokens per session scan A 76c0e501f693
fizzy-workflow is a skill published in the GitHub repository keskinonur/claude-plugin-fizzy (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 388 once invoked, about $0.0003 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 skills, from other repositories
implement_plan
Implement technical plans from thoughts/shared/plans with verification.
implement_task
Implementation agent that executes a single task and creates handoff on completion.
migrate
Migration workflow - research → analyze → plan → implement → review.
index-at-creation
Index artifacts when they're created, not at batch boundaries.
atl-fetch-jira
A command-line tool for retrieving Jira issues from Atlassian Cloud, including their details, comments, change history, and attachments.
manage-flows
Manage flow lifecycle - publish, test, batch operations, inventory reports. Use when the user asks to publish, test, batch manage, or get an inventory of flows.