Borrowing it
Nothing to install: this file belongs to shelizi/coding-tools-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shelizi/coding-tools-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/shelizi/coding-tools-mcpWrote 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/shelizi/coding-tools-mcp/agents-md)<a href="https://agentmods.dev/instructions/shelizi/coding-tools-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/shelizi/coding-tools-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/shelizi/coding-tools-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/shelizi/coding-tools-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01353 | $0.01353 |
| Opus 5.5 | $0.00541 | $0.00541 |
| Sonnet 5.5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
coding-tools-mcp 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP (call first)
Requires mcp-probe-kit. Before coding, read Skill: @.agents/skills/mcp-probe-kit/SKILL.md (or When to call MCP) (Skill file auto-created on first MCP call).
- Unsure which MCP →
workflow(returns firstTool) - Feature →
start_feature(searches memory first) - Bug →
start_bugfix(searches memory first) - UI →
start_ui(searches memory first) - Unfamiliar code / impact →
code_insight(context / impact / auto) - Missing context →
init_project_context - Commit →
gencommit
Context: before coding read project-context (links to docs/project-context/)
Graph: read latest before large changes; refresh code_insight mode=auto save_to_docs=true
Memory (requires MEMORY_* env):
- Search:
start_*auto-injects full memory hits; usesearch_memorymid-task;read_memory_assetfor a specific id - Store: do NOT use source_project/source_path for cross-repo pools; put paths in content; write keyword-rich summary
- Update: fix existing entries in place with
update_memory_assetby asset_id (preserves ID) - Cleanup: remove stale/wrong/duplicate entries with
delete_memory_asset(confirm viaread_memory_assetfirst) - After verified bugfix → MUST
memorize_assettype=bugfix(sections: symptom, root cause, fix, verification) - Reusable feature/UI →
memorize_assettype=pattern/component
GitNexus — Code Intelligence
This project is indexed by GitNexus as coding-tools-mcp (2497 symbols, 5234 relationships, 210 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
If any GitNexus tool warns the index is stale, run
npx gitnexus analyzein terminal first.
Always Do
- MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run
gitnexus_impact({target: "symbolName", direction: "upstream"})and report the blast radius (direct callers, affected processes, risk level) to the user. - MUST run
gitnexus_detect_changes()before committing to verify your changes only affect expected symbols and execution flows. - MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
- When exploring unfamiliar code, use
gitnexus_query({query: "concept"})to find execution flows instead of grepping. It returns process-grouped results ranked by relevance. - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use
gitnexus_context({name: "symbolName"}).
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.
- 1mo ago Changed · +4 lines · +70 tokens per session c7c6319ca37d
- 1mo ago First seen · 76 lines · 1,283 tokens per session scan A 019bc5fd5996
coding-tools-mcp AGENTS.md is an instructions file published in the GitHub repository shelizi/coding-tools-mcp (0 stars, last pushed 8d ago), licensed Apache-2.0. It adds 1,353 tokens to every session, about $0.0054 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.