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/vkirill/agent-consult/agents-mdgit clone --depth 1 https://github.com/VKirill/agent-consultWrote 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/vkirill/agent-consult/agents-md)<a href="https://agentmods.dev/instructions/vkirill/agent-consult/agents-md"><img src="https://agentmods.dev/badge/instructions/vkirill/agent-consult/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.00697 | $0.00697 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
agent-consult 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus — Code Intelligence
This project is indexed by GitNexus as agent-consult (547 symbols, 885 relationships, 44 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
Index stale? Run
node .gitnexus/run.cjs analyzefrom the project root — it auto-selects an available runner. No.gitnexus/run.cjsyet?npx gitnexus analyze(npm 11 crash →npm i -g gitnexus; #1939).
Always Do
- MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run
impact({target: "symbolName", direction: "upstream"})and report the blast radius (direct callers, affected processes, risk level) to the user. - MUST run
detect_changes()before committing to verify your changes only affect expected symbols and execution flows. For regression review, compare against the default branch:detect_changes({scope: "compare", base_ref: "main"}). - MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
- When exploring unfamiliar code, use
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
context({name: "symbolName"}).
Never Do
- NEVER edit a function, class, or method without first running
impacton it. - NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
- NEVER rename symbols with find-and-replace — use
renamewhich understands the call graph. - NEVER commit changes without running
detect_changes()to check affected scope.
Resources
| Resource | Use for |
|---|---|
gitnexus://repo/agent-consult/context |
Codebase overview, check index freshness |
gitnexus://repo/agent-consult/clusters |
All functional areas |
gitnexus://repo/agent-consult/processes |
All execution flows |
gitnexus://repo/agent-consult/process/{name} |
Step-by-step execution trace |
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 · 44 lines · 697 tokens per session scan A 9394276d1831
agent-consult AGENTS.md is an instructions file published in the GitHub repository VKirill/agent-consult (1 stars, last pushed 2mo ago), licensed MIT. It adds 697 tokens to every session, about $0.0035 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
mem0-mcp CLAUDE.md
Claude Code instructions for andresmorales07/mem0-mcp, covering claude.md, what this is, commands, manual smoke test against a running mem0 instance and architecture.
mcp-deadmansnitch CLAUDE.md
Instructions for jamesbrink/mcp-deadmansnitch, covering claude.md, dead man's snitch mcp server, essential commands, run tests (uses pytest-asyncio in auto mode) and type checking and linting.
obsidian-mcp-server AGENTS.md
AGENTS.md instructions for nbaradar/obsidian-mcp-server, covering obsidian mcp server — agents.md, purpose, implementation plan, resources (planned) and tools (current).
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
powerbi-mcp CLAUDE.md
Instructions for sulaiman013/powerbi-mcp, covering claude.md and developer notes.
minecraft-dev-mcp AGENTS.md
Instructions for MCDxAI/minecraft-dev-mcp, covering agent handbook – minecraft dev mcp, project snapshot, what agents should prioritize, architecture wayfinder (src/) and available mcp tools (for llm surfaces).