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-writegit 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-write)<a href="https://agentmods.dev/skills/rijul1204/rashedul-agentic-engineering/fizzy-write"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/fizzy-write/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-write"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/fizzy-write.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.00090 | $0.01827 |
| Opus 5.5 | $0.00036 | $0.00731 |
| Sonnet 5.5 | $0.00018 | $0.00365 |
| Haiku 4.5 | $0.00009 | $0.00183 |
Grade A, and why
fizzy-write 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 1mo 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.
Use `curl` with the Bearer token. All endpoints are under `https://app.fizzy.do`. How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fizzy Write — Manage Cards & Boards
Create and manage cards, boards, comments, and assignments in the Fizzy task board.
Credentials
Bearer token:
eCaGiEZPirmuqVQwuNmCMNd6
Account ID: 6132669
Base URL: https://app.fizzy.do
Known Boards
| Board ID | Name | Default? |
|---|---|---|
| 03fd4omd9qico7wmyyof5yfe4 | QA Board | YES |
If the user names a specific board, resolve it by calling
GET /6132669/boardsand matching by name. Otherwise, always use the QA board.
Workflow
Step 1 — Parse the user's intent
Identify the operation:
| Intent | Operation |
|---|---|
| "create a card / task" | Create card |
| "create a board" | Create board |
| "update / edit card #N" | Update card |
| "close / done card #N" | Close card |
| "reopen card #N" | Reopen card |
| "comment on card #N" | Add comment |
| "assign card #N to [user]" | Assign |
| "move card #N to [column]" | Triage (move) |
| "tag card #N with [tag]" | Apply tag |
For create card: extract title, optional description, optional board name (defaults to QA board). For create board: extract board name and optional description.
IMPORTANT — Fizzy does NOT support Markdown. Do not use
**bold**,# headers,- bulletsyntax, or any Markdown in card titles, descriptions, or comments. Use plain text with spacing and line breaks for structure. Example:Implementation notes: - Check user region against Dots coverage map - Block enrollment if region unsupported - Show clear error message to playerUse indentation and blank lines for readability — not Markdown syntax.
Step 2 — Execute the API call
Use curl with the Bearer token. All endpoints are under https://app.fizzy.do.
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.
- 1mo ago First seen · 213 lines · 90 tokens per session scan A 8587b020058c
fizzy-write is a skill published in the GitHub repository Rijul1204/rashedul-agentic-engineering (2 stars, last pushed 3mo ago), licensed MIT. It adds 90 tokens to every session and 1,827 once invoked, about $0.0004 per session on Opus 5.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, each phase's stages defined up front in one run, 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…