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 Rijul1204/rashedul-agentic-engineering --skill fizzy-product-managergit clone --depth 1 https://github.com/Rijul1204/rashedul-agentic-engineeringWrote 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/rijul1204/rashedul-agentic-engineering/fizzy-product-manager)<a href="https://agentmods.dev/skills/rijul1204/rashedul-agentic-engineering/fizzy-product-manager"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/fizzy-product-manager/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/rijul1204/rashedul-agentic-engineering/fizzy-product-manager"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/fizzy-product-manager.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.00030 | $0.01021 |
| Opus 5 | $0.00015 | $0.00511 |
| Sonnet 5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
fizzy-product-manager scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For multi-step curl workflows (triage sessions, health checks, bulk operations), load the [./rules/api-recipes.md](./rules/api-recipes.md) file. How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use this skill whenever you are managing Fizzy Kanban boards, triaging cards, running board health checks, generating reports, or performing any product management task via the Fizzy API.
API Reference
The full Fizzy API specification is at docs/fizzy-api.md. Load it when you need complete endpoint details, request/response schemas, or parameter references.
Kanban principles
When applying Kanban methodology to board management, load the ./rules/kanban-principles.md file.
Tap Games operating defaults
When you need Tap Games-specific board templates, ticket templates, working procedure, or code-aware triage defaults, load the ./rules/tap-games-context.md file.
Board triage
When processing the triage queue (Maybe? cards), load the ./rules/card-triage.md file for the decision framework and batch workflow.
Board hygiene
For routine board maintenance and health checks, load the ./rules/board-hygiene.md file for the 7-step weekly checklist.
Reports
When generating board status reports, activity summaries, or workload breakdowns, load the ./rules/board-reports.md file.
API recipes
For multi-step curl workflows (triage sessions, health checks, bulk operations), load the ./rules/api-recipes.md file.
Jira migration (one-time cutover)
When executing the Fizzy → Jira migration for Tap Games, load the ./rules/jira-migration.md file. It is the single-use runbook for the cutover into the TG project on globalcompetitionworld.atlassian.net. Remove the file (and this pointer) after Phase 4 completes.
How to use
Read individual rule files for detailed explanations, API examples, and workflows:
- rules/api-basics.md - Token setup, URL structure, pagination, caching, and error handling
- rules/kanban-principles.md - 4 Kanban principles and 6 core practices applied to Fizzy
- rules/board-management.md - Creating, configuring, publishing, and organizing boards
- rules/column-structure.md - Designing workflow columns, colors, and common patterns
- rules/card-lifecycle.md - Full card lifecycle from triage through closure
- rules/card-triage.md - Triage decision framework and batch processing workflow
- rules/card-writing.md - Best practices for card titles, descriptions, and rich text
- rules/card-details.md - Steps (todos), reactions (boosts), and pins
- rules/tagging-strategy.md - Tag taxonomy, naming conventions, and filtering
- rules/assignments-workload.md - Assignment management and workload balancing
- rules/wip-limits.md - WIP limit theory and enforcement via API monitoring
- rules/entropy-management.md - Auto-postpone system and stale card handling
- rules/board-hygiene.md - 7-step weekly board maintenance checklist
- rules/board-reports.md - Board snapshots, velocity, health, and workload reports
- rules/comments-collaboration.md - Using comments for PM communication and status updates
- rules/webhooks-automation.md - Real-time webhook setup for external integrations
- rules/api-recipes.md - Complete multi-step curl recipes for common PM workflows
- rules/tap-games-context.md - Team-specific context: boards, members, conventions, templates, code-aware triage defaults
- rules/jira-migration.md - One-time Fizzy → Jira (
TGproject on GCW) cutover runbook
What ships with it
19 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.
- rules/api-basics.md 3.4 KB
- rules/api-recipes.md 6.8 KB
- rules/assignments-workload.md 2.6 KB
- rules/board-hygiene.md 4.0 KB
- rules/board-management.md 2.8 KB
- rules/board-reports.md 3.3 KB
- rules/card-details.md 3.7 KB
- rules/card-lifecycle.md 3.6 KB
- rules/card-triage.md 3.6 KB
- rules/card-writing.md 3.3 KB
- rules/column-structure.md 2.6 KB
- rules/comments-collaboration.md 2.7 KB
- rules/entropy-management.md 3.0 KB
- rules/jira-migration.md 14 KB
- rules/kanban-principles.md 3.4 KB
- rules/tagging-strategy.md 2.4 KB
- rules/tap-games-context.md 12 KB
- rules/webhooks-automation.md 3.6 KB
- rules/wip-limits.md 2.8 KB
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 · 67 lines · 30 tokens per session scan A e885127c924f
fizzy-product-manager is a skill published in the GitHub repository Rijul1204/rashedul-agentic-engineering (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,021 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
mass-ulw
Drives dependency-ordered child work through the native workflow tool, one run per phase with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…
roadmap-planning
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next…