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 insodimension/awesome-agent-protocols --skill agent-protocolsgit clone --depth 1 https://github.com/insodimension/awesome-agent-protocolsWrote 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/insodimension/awesome-agent-protocols/agent-protocols)<a href="https://agentmods.dev/skills/insodimension/awesome-agent-protocols/agent-protocols"><img src="https://agentmods.dev/badge/skills/insodimension/awesome-agent-protocols/agent-protocols.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.1 | $0.00163 | $0.03244 |
| Opus 5 | $0.00081 | $0.01622 |
| Sonnet 5 | $0.00033 | $0.00649 |
| Haiku 4.5 | $0.00016 | $0.00324 |
Grade A, and why
agent-protocols 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 7d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Protocols
Guides agent/harness engineering toward using, extending, and contributing to established AI agent protocol standards rather than inventing ad-hoc solutions.
Knowledge base: This skill lives inside the awesome-agent-protocols repo, which catalogs 53+ protocols across 11 stack layers. The catalog is the source of truth; this skill makes it actionable during development.
This skill is self-improving. Every run must end with a gotcha review (see Self-Improvement Protocol).
This skill is a checklist, not a suggestion. Every mode below is a numbered checklist. You MUST tick each
[ ]by writing its status + exit-criterion outcome in your response BEFORE moving to the next step. Skipping a step without documenting why is a skill violation.
Pre-flight — ALWAYS (before any mode)
- PF-1. Read references/gotchas.md. Exit: you can state the 3 most recent dated entries in one sentence each (or confirm the log is empty).
- PF-2. Read the protocol catalog. Read the repo's
README.md(two levels up from this skill) to load the current protocol taxonomy. Exit: you can name the 11 stack layers. - PF-3. Read the decision tree. Read references/decision-tree.md. Exit: you can map the 10 primary "you're building..." rows to their protocols.
- PF-4. Understand the user's context. What are they building? What layer of the stack? What's the integration target? Exit: one sentence stating the task and its stack layer.
- PF-5. Pick the mode. Exit: one of Recommend / Lookup / Audit / Contribute written down.
Modes
| Mode | When to use | Output |
|---|---|---|
| Recommend | User is building something and needs to know which protocol(s) apply | Protocol recommendation with rationale + wire examples |
| Lookup | User wants spec details, wire messages, or examples for a specific protocol | Spec summary + verbatim wire examples from examples/ |
| Audit | User has existing code and wants to check protocol compliance or find protocol opportunities | Compliance report + specific recommendations |
| Contribute | User built something protocol-adjacent and wants to contribute back | Contribution path: which spec, which repo, what format |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 193 lines · 163 tokens per session scan A 849055cf73f5
agent-protocols is a skill published in the GitHub repository insodimension/awesome-agent-protocols (9 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 163 tokens to every session and 3,244 once invoked, about $0.0008 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-31.
Other skills, from other repositories
design-taste-frontend
Use for visual design direction on greenfield, user-facing surfaces — marketing and landing pages, generated apps, portfolio-style or standalone pages. NOT for routine Archestra platform UI work (dashboards, data tables, settings, forms, existing components) — use archestra-dev-frontend for that. Upstream intent…
migrate-to-archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.
archestra-dev-backend-tests
Use when writing or modifying Archestra backend unit tests (platform/backend/src//.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
archestra-dev-rust-napi
Use when editing Rust in this repo — the NAPI crates under platform/archestra-rs (app-runtime, image, and sandbox core/-rs crate pairs plus napi-loader, with their generated TypeScript bindings) or the standalone ai-labs Rust workspace (core/runner/cli/analyzer/dashboard) — including Rust build/test checks.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.