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/basecamp/fizzy-cli/agents-mdgit clone --depth 1 https://github.com/basecamp/fizzy-cliWhat 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.01575 | $0.01575 |
| Opus 5 | $0.00788 | $0.00788 |
| Sonnet 5 | $0.00315 | $0.00315 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
fizzy-cli 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fizzy CLI Development Context
Repository Structure
fizzy-cli/
├── cmd/fizzy/ # Main entrypoint
├── internal/
│ ├── client/ # Legacy HTTP client (upload, download, multipart, migrate)
│ ├── commands/ # Command implementations
│ ├── config/ # Configuration management
│ ├── errors/ # Error handling and types
│ ├── mcpserver/ # `fizzy mcp` MCP server (catalog/ synced from fizzy-mcp-server)
│ └── render/ # Output rendering (styled, markdown, columns)
├── e2e/ # Go integration tests
├── skills/ # Agent skills
└── .claude-plugin/ # Claude Code integration
SDK Architecture
Commands use the fizzy-sdk (github.com/basecamp/fizzy-sdk/go/pkg/fizzy) for API access:
getSDK()returns*fizzy.AccountClient— account-scoped SDK client for most commandsgetSDKClient()returns*fizzy.Client— root client for account-independent operations (e.g. identity)getClient()(deprecated) returnsclient.API— legacy client, used only for file upload, download, multipart PATCH, and board migration
SDK service methods return typed structs (e.g. *generated.Board, []generated.Card). Helper functions convert to the any types the output layer expects:
normalizeAny(data)— JSON-round-trips any value (typed structs,json.RawMessage, maps) tomap[string]any/[]map[string]anyjsonAnySlice(pages)— converts[]json.RawMessagefromGetAll()pagination to[]map[string]anyconvertSDKError(err)— converts SDK errors to*output.ErrortoSliceAny(v)— normalizes[]map[string]anyor[]anyto[]anyfor iteration
Account can be a slug or numeric ID.
Fizzy API Reference
API documentation: https://github.com/basecamp/fizzy/blob/main/docs/API.md
Key endpoints used by the CLI:
/boards.json- List boards/cards.json?board_ids[]=<id>- Cards on a board/cards/{number}.json- Show card by number/cards.json?terms[]=<query>- Search cards by text
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.
- 2d ago First seen · 128 lines · 1,575 tokens per session scan A 554b7a019694
fizzy-cli AGENTS.md is an instructions file published in the GitHub repository basecamp/fizzy-cli (221 stars, last pushed 4d ago), licensed MIT. It adds 1,575 tokens to every session, about $0.0079 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-30.
Other instructions, from other repositories
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.