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/resolve-ai-oss/resolve-ai-plugins/agents-mdgit clone --depth 1 https://github.com/resolve-ai-oss/resolve-ai-pluginsWrote 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/resolve-ai-oss/resolve-ai-plugins/agents-md)<a href="https://agentmods.dev/instructions/resolve-ai-oss/resolve-ai-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/resolve-ai-oss/resolve-ai-plugins/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.00507 | $0.00507 |
| Opus 5 | $0.00253 | $0.00253 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
resolve-ai-plugins 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resolve-ai-plugins CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve AI Plugin Guidance
Skill vs Tool Description Boundary
Skills are shipped less often than MCP tools and server behavior. Keep skills focused on stable workflow guidance:
- When to use a workflow and when to hand off to another skill.
- How to translate user intent into the right class of tool call.
- How to compose high-quality prompts/messages from local context.
- Human-facing output shape and follow-up behavior.
- Confirmation gates for mutating or credit-consuming actions.
- Host-specific execution hints only when the host truly differs.
Put volatile or API-specific details in MCP tool descriptions or server-side code instead:
- Exact parameters, enums, defaults, limits, sort order, and return fields.
- Stream protocol details, including terminal markers and failure semantics.
- REST endpoints, payload schemas, authentication, and feature gates.
- Current backend limitations or behavior that can change independently of plugin releases.
- Tool-specific examples that are mostly schema examples rather than workflow examples.
Shared stream-command behavior belongs in the MCP server instructions, condensed; ask carries the full execution semantics since tool descriptions arrive complete at call time. Other tool descriptions should only say whether the tool returns a stream_command and what live state it follows.
If a skill starts restating a tool schema, trim the skill and improve the server instructions or tool description instead.
Host size limits
Hosts truncate MCP guidance text: Claude Code cuts server instructions and each tool description at 2KB; Codex prioritizes the first 512 characters of instructions. Keep server instructions under 2KB with the most important guidance first (enforced by packages/svc-mcp-server/__tests__/v2HttpTransport.test.ts). Never duplicate text between instructions and a tool description — the instructions copy is the one at truncation risk, so it should hold only cross-tool guidance.
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.
- 4d ago First seen · 46 lines · 507 tokens per session scan A 952273058c3c
resolve-ai-plugins AGENTS.md is an instructions file published in the GitHub repository resolve-ai-oss/resolve-ai-plugins (4 stars, last pushed 10d ago), licensed Apache-2.0. It adds 507 tokens to every session, about $0.0025 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 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.