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 agentmods add instructions/procube-cx/fizzy-mcp/agents-mdgit clone --depth 1 https://github.com/procube-cx/fizzy-mcpWrote 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/instructions/procube-cx/fizzy-mcp/agents-md)<a href="https://agentmods.dev/instructions/procube-cx/fizzy-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/procube-cx/fizzy-mcp/agents-md.svg" alt="Measured on agentmods" 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 | $0.01040 | $0.01040 |
| Opus 5 | $0.00520 | $0.00520 |
| Sonnet 5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
fizzy-mcp AGENTS.md 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 3d 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.
This is a copy
86% identical to fizzy-mcp AGENTS.md — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.local.md
AGENTS.md
Project Overview
fizzy-mcp is an MCP (Model Context Protocol) server for the Fizzy project management tool. It exposes 40+ tools for managing boards, cards, columns, steps, comments, reactions, tags, and notifications.
Tech Stack
- Language: TypeScript 5.7 (ES2022, ESM modules)
- Runtime: Node.js 18+ (standard), Cloudflare Workers (production)
- MCP SDK: @modelcontextprotocol/sdk
- Validation: Zod
- Testing: Vitest
- Build: tsc (compile), tsx (dev)
Architecture
src/
├── index.ts # CLI entry point, transport selection
├── server.ts # MCP server setup, tool registration
├── client/
│ ├── fizzy-client.ts # HTTP client with retry, ETag caching
│ └── types.ts # API request/response interfaces
├── tools/
│ ├── definitions.ts # Tool metadata (name, description, annotations)
│ ├── schemas.ts # Zod input schemas
│ └── handlers.ts # Tool execution logic
├── transports/
│ ├── stdio.ts # IDE integrations (Cursor, VS Code)
│ ├── sse.ts # Server-Sent Events (multi-user)
│ └── http.ts # Streamable HTTP (multi-user)
├── utils/
│ ├── errors.ts # Typed error classes (FizzyAPIError, etc.)
│ ├── logger.ts # Structured stderr logging
│ ├── security.ts # CORS, auth, localhost binding
│ ├── session-manager.ts
│ └── etag-cache.ts
└── cloudflare/ # Workers deployment (Durable Objects)
Key flow
server.tsregisters tools fromtools/definitions.ts- Each tool call dispatches through
executeToolHandler()intools/handlers.ts - Handlers call
FizzyClientmethods which make HTTP requests to the Fizzy API - Responses are formatted as MCP text content
Tool system
Tools are defined across three files that must stay in sync:
definitions.ts— tool name, title, description, schema reference, annotationsschemas.ts— Zod schema for input validation (field names here are what MCP clients send)handlers.ts— flatRecord<toolName, handler>mapping; maps MCP args to client method calls
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.
- 3d ago First seen · 97 lines · 1,040 tokens per session scan A a6697c52bd4d
fizzy-mcp AGENTS.md is an instructions file published in the GitHub repository procube-cx/fizzy-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,040 tokens to every session, about $0.0052 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to fizzy-mcp AGENTS.md, differing in 9 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.