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/wate/openapi-mcp/yamlgit clone --depth 1 https://github.com/wate/openapi-mcpWhat 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.00497 | $0.00497 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
openapi-mcp yaml.instructions.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 yesterday.
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
YAMLファイル作成・編集指針
コーディング規約
以下のルールは必ず遵守してください。
基本フォーマット
- インデントはスペースを使用し、タブは使用しない
- インデント幅は2スペースで統一する
構文・記法
- キーと値の区切りは
key: value形式で記述する - インライン記法の
{}や[]内のスペースは最小限にする - 真偽値は
true/falseを使用する - 先頭0付き数値など曖昧な数値表現を避ける
- 同一階層でキー名を重複させない
空行ルール
- リスト項目(
- item)の直前に不要な空行を入れない - ハッシュ項目(
key: value)の直前に不要な空行を入れない - 同一階層の連続する項目は空行なしで連続記述する
- 意味的なセクション区切り以外では空行を入れない
- 空行を使う場合でも連続空行は作らない
品質基準
- YAML 1.2として構文エラーがないこと
.yamllint.ymlの設定に適合すること- インデント、空行、スペーシングがファイル全体で一貫していること
- 人が読んだときに階層構造を追跡しやすいこと
禁止事項
- タブ文字によるインデント
- 同一階層の項目間への過剰な空行挿入
- リストやハッシュの各項目の前に毎回空行を入れる記述
- 重複キーの定義
- 暗黙的な8進数として解釈される数値表現
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.
- yesterday First seen · 50 lines · 497 tokens per session scan A 9e5fea1a027d
openapi-mcp yaml.instructions.md is an instructions file published in the GitHub repository wate/openapi-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 497 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
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.