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 skills/stevesolun/ctx/agents-md-protocolnpx skills add stevesolun/ctx --skill agents-md-protocolgit clone --depth 1 https://github.com/stevesolun/ctxWrote 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/stevesolun/ctx/agents-md-protocol)<a href="https://agentmods.dev/skills/stevesolun/ctx/agents-md-protocol"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/agents-md-protocol.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.00059 | $0.00383 |
| Opus 5 | $0.00030 | $0.00192 |
| Sonnet 5 | $0.00012 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
agents-md-protocol 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.
What it actually says
AGENTS.md Protocol
Purpose
Create or tighten a repository-level AGENTS.md contract for coding agents.
Treat it as durable operating context, not a chat prompt.
When to Use
- Repo has no
AGENTS.md,CLAUDE.md, or equivalent agent instructions. - Existing instructions are stale, vague, or missing test commands.
- A custom/API/local harness needs stable context it can load every run.
- A multi-agent workflow needs explicit handoff and review rules.
Procedure
- Inspect repo layout, package managers, CI files, and test commands.
- Capture only durable facts and team rules.
- Keep commands exact and runnable from the documented directory.
- Add security and destructive-operation boundaries.
- Add PR/review expectations and required verification.
- Keep the file short enough to load every session.
Recommended Sections
Dev environment tipsTesting instructionsBuild and lintCode styleSecurity boundariesPR instructionsAgent handoff notes
Quality Bar
- Every command has a working directory or clear scope.
- No secrets, tokens, or private URLs.
- No vague rules such as "be careful" without a concrete check.
- No roadmap or marketing text.
- Instructions match current CI and package metadata.
Harness Attachment
For non-Claude-Code harnesses, load AGENTS.md as outer-loop project context.
The harness should also keep explicit task state outside conversation history.
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 · 55 lines · 59 tokens per session scan A a75b8733d1c2
agents-md-protocol is a skill published in the GitHub repository stevesolun/ctx (583 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 383 once invoked, about $0.0003 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 skills, from other repositories
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…
haiku
When writing a haiku for this bot, follow these conventions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…