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-board-monitorgit 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-board-monitor)<a href="https://agentmods.dev/skills/rijul1204/rashedul-agentic-engineering/fizzy-board-monitor"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/fizzy-board-monitor/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-board-monitor"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/fizzy-board-monitor.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.00084 | $0.00987 |
| Opus 5 | $0.00042 | $0.00494 |
| Sonnet 5 | $0.00017 | $0.00197 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
fizzy-board-monitor 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 12d 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.
curl -s "https://app.fizzy.do/6132669/boards" \ How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fizzy Board Monitor — On-Demand Board Overview
Display an on-demand Kanban-style overview of any Fizzy board, with cards grouped by column.
Credentials
Bearer token: R2Rek4vNLSrr12F9QFkBy3BZ
Account ID: 6132669
Base URL: https://app.fizzy.do
Known Boards
| Board ID | Name | Default? |
|---|---|---|
| 03fd4omd9qico7wmyyof5yfe4 | QA Board | YES |
Default behaviour: always show the QA board unless the user explicitly names a different board.
Workflow
Step 1 — Determine target board
- If the user says "show the board" or "fizzy board" with no board name → use QA board (
03fd4omd9qico7wmyyof5yfe4) - If the user names a board (e.g., "show the backend sprint board") → list all boards and match by name:
curl -s "https://app.fizzy.do/6132669/boards" \
-H "Accept: application/json" \
-H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"
Step 2 — Fetch columns
curl -s "https://app.fizzy.do/6132669/boards/<BOARD_ID>/columns" \
-H "Accept: application/json" \
-H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"
Note column IDs and names (e.g., "To Do", "In Progress", "Done").
Step 3 — Fetch open cards
curl -s "https://app.fizzy.do/6132669/cards?board_ids[]=<BOARD_ID>&status=open" \
-H "Accept: application/json" \
-H "Authorization: Bearer R2Rek4vNLSrr12F9QFkBy3BZ"
Follow Link: rel="next" headers for pagination if the board has many cards.
Step 4 — Group cards by column
Map each card to its column using the card's column_id field. Count cards per column.
Step 5 — Present the Kanban overview
Fizzy Board — QA Board (YYYY-MM-DD HH:MM)
https://app.fizzy.do/6132669/boards/03fd4omd9qico7wmyyof5yfe4
┌─────────────────────────────────────────────────────────────┐
│ TO DO (3) │ IN PROGRESS (2) │ DONE (5) │
├─────────────────────────────────────────────────────────────┤
│ #45 Game disconnect│ #42 Payment retry │ #38 Admin label │
│ #44 Seed script │ #41 JWKS 500 │ #37 Leaderboard │
│ #43 Refactor auth │ │ ... │
└─────────────────────────────────────────────────────────────┘
Total open: 5 | Closed today: 5
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.
- 12d ago First seen · 105 lines · 84 tokens per session scan A c6d0069b29fa
fizzy-board-monitor is a skill published in the GitHub repository Rijul1204/rashedul-agentic-engineering (2 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 987 once invoked, about $0.0004 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
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.…
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…
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…