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/hi0001234d/coding-agent-mcp-tools/claude-mdgit clone --depth 1 https://github.com/hi0001234d/coding-agent-mcp-toolsWrote 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/hi0001234d/coding-agent-mcp-tools/claude-md)<a href="https://agentmods.dev/instructions/hi0001234d/coding-agent-mcp-tools/claude-md"><img src="https://agentmods.dev/badge/instructions/hi0001234d/coding-agent-mcp-tools/claude-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.1 | $0.00688 | $0.00688 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
coding-agent-mcp-tools CLAUDE.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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
coding-agent-mcp-tools — Claude Code Instructions
This repo is a curated list of coding agents and MCP tools. It has TWO special workflows: Idea Validation and Auto Research.
TOOL 1: Idea Validation (via idea-reality-mcp + README scan)
When someone says "validate idea: X" or "is X worth building?", run this flow:
Step 1 — idea_check via MCP
Call the idea_check MCP tool with the idea description.
Use depth="deep" for thorough validation.
Step 2 — Scan THIS repo's list (THE MOST IMPORTANT STEP)
Go through the README.md of THIS repo (coding-agent-mcp-tools). For EVERY repo listed, do:
- Fetch its GitHub URL (listed in README)
- Read its README content (use WebFetch tool)
- Check if the idea overlaps with what that repo does
Step 3 — Decision Logic
NEGATIVE (not worth building):
- If 2+ repos in our list already cover the idea's core capability
- State which repos cover it and why
- Format: "NEGATIVE — Already covered by [repo-name]: [reason from their README]"
POSITIVE (worth building):
- If NO repo in our list covers this specific angle
- Format: "POSITIVE — Gap identified: [reason]. Closest existing: [repo] but differs because [difference]"
PARTIAL (niche opportunity):
- Core idea exists but this specific angle is unique
- Format: "PARTIAL — Core exists in [repo], but [specific angle] is not covered"
Step 4 — Final Report Format
IDEA: [idea name]
DECISION: [POSITIVE / NEGATIVE / PARTIAL]
MCP Signal: [reality_signal]/100 — [duplicate_likelihood]
Top Similar (from MCP): [list top_similars]
Internal Repo Scan:
- [repo-name] ([link]): [relevant/not-relevant] — [one line reason]
REASONING:
[2-3 sentences explaining the decision]
VERDICT:
[Final recommendation]
TOOL 2: Auto Research (via autoresearch skill)
When someone says "research: X" or "find repos for: X", use the /autoresearch skill.
Research Pattern Examples:
RAG with vision support:
/autoresearch
Goal: Find repos in our list that support RAG with BOTH text AND vision/image documents
Scope: README.md (read-only, do not modify)
Metric: count of repos found matching criteria (higher is better)
Verify: node -e "const r=require('./research-results.json');console.log('SCORE: '+r.length)"
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.
- 6d ago First seen · 88 lines · 688 tokens per session scan A 19a67c027b6d
coding-agent-mcp-tools CLAUDE.md is an instructions file published in the GitHub repository hi0001234d/coding-agent-mcp-tools (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 688 tokens to every session, about $0.0034 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).
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.
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
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.