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/zhensherlock/protocol-launcher/agents-mdgit clone --depth 1 https://github.com/zhensherlock/protocol-launcherWrote 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/zhensherlock/protocol-launcher/agents-md)<a href="https://agentmods.dev/instructions/zhensherlock/protocol-launcher/agents-md"><img src="https://agentmods.dev/badge/instructions/zhensherlock/protocol-launcher/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.01386 | $0.01386 |
| Opus 5 | $0.00693 | $0.00693 |
| Sonnet 5 | $0.00277 | $0.00277 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
protocol-launcher 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Protocol Launcher
Repo Shape
- PNPM workspace + Turbo monorepo; main CI uses Node 22 and
packageManageris[email protected](npm-publish builds with Node 22, then publishes the packed tgz with Node 24). - Workspaces are
packages/shared(qs,encodeUrlPayload),packages/protocol-launcher(published URL generator library),apps/docs(VitePress EN/ZH docs), andapps/promo-video(HyperFrames composition). - The root package and library package are both named
protocol-launcher; use path filters likepnpm --filter ./packages/protocol-launcher build, not name filters. - Respect nested workspace instructions before editing package/app code:
packages/shared/AGENTS.md,packages/protocol-launcher/AGENTS.md,apps/docs/AGENTS.md, andapps/promo-video/AGENTS.md. - Build outputs are ignored (
dist,coverage,apps/docs/.vitepress/dist,apps/docs/.vitepress/cache,.turbo,apps/*/renders,apps/*/.thumbnails,apps/*/.waveform-cache); do not edit generated output.
Commands That Matter
- Install:
pnpm install. - Root dev loop:
pnpm devruns Turbo with--filter=./apps/*..., so docs, promo-video, and dependency package watchers start together. Use focused dev commands when you only need one app. - Focused dev:
pnpm --filter ./apps/docs devfor VitePress,pnpm --filter ./apps/promo-video devfor HyperFrames preview. - CI-equivalent build/test:
pnpm buildthenpnpm coverage; the build workflow runs both and deploysapps/docs/.vitepress/dist. - Root
pnpm buildonly filters./apps/docs...; promo video is separate viapnpm build:promo,pnpm check:promo, andpnpm render:promo. - Focused builds:
pnpm --filter ./packages/shared build,pnpm --filter ./packages/protocol-launcher build,pnpm --filter ./apps/docs build. - Tests:
pnpm testfor all Vitest projects; focus withpnpm test packages/protocol-launcher/tests/vscode.test.ts,pnpm test vscode, orpnpm test -t "test name". - Coverage gate:
pnpm coveragematches the build workflow's test step. - Formatting/linting: there is no root lint script; use
npx biome check .ornpx biome check --write .. Pre-commit only runsbiome check --writeon stagedpackages/**/*.{ts,js}. - Type checking: do not use bare
npx tsc --noEmitfrom the root; there is no roottsconfig.jsonandtsconfig.root.jsonis the shared base. Use package builds ornpx tsc -p packages/protocol-launcher/tsconfig.json --noEmit.
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.
- 5d ago First seen · 52 lines · 1,386 tokens per session scan A 56a48ce02685
protocol-launcher AGENTS.md is an instructions file published in the GitHub repository zhensherlock/protocol-launcher (127 stars, last pushed 7d ago), licensed MIT. It adds 1,386 tokens to every session, about $0.0069 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
AgentNetworkProtocol AGENTS.md
AGENTS.md instructions for agent-network-protocol/AgentNetworkProtocol, covering repository guidelines, project structure & module organization, protocol ownership boundary, build, test, and development commands and coding style & naming conventions.
Cotal AGENTS.md
AGENTS.md instructions for Cotal-AI/Cotal, covering agents.md, what this is, read these first, commands and repository map.
storagesdk AGENTS.md
Instructions for storagesdk/storagesdk, covering agents.md, what this is, locked design decisions, working principles and gates.
Cotal CLAUDE.md
Claude Code instructions for Cotal-AI/Cotal: This repo uses AGENTS.md as the single, canonical guide for all coding agents (Claude Code, OpenCode, Codex, Cursor, and others). Read it first.
sint-protocol CLAUDE.md
Instructions for sint-ai/sint-protocol, covering sint protocol — agent guide, what is this?, quick commands, monorepo layout and architecture rules.
sint-protocol AGENTS.md
Instructions for sint-ai/sint-protocol, covering sint protocol — ai agent guide, what this repo does, key invariants (never violate these), quick orientation and package dependency graph.