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/cajasmota/grafel/claude-mdgit clone --depth 1 https://github.com/cajasmota/grafelWrote 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/cajasmota/grafel/claude-md)<a href="https://agentmods.dev/instructions/cajasmota/grafel/claude-md"><img src="https://agentmods.dev/badge/instructions/cajasmota/grafel/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.00735 | $0.00735 |
| Opus 5 | $0.00367 | $0.00367 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
grafel 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use grafel MCP vs grep
grafel MCP gives you a navigable, accurate map of the code; grep gives you raw pattern matches.
Use MCP for structural questions: who calls X? what is the flow? where does Y live in the graph?
Use grep for raw enumeration: every if err != nil, every import line, every TODO.
Pair them: MCP narrows the search space; grep verifies edge-property questions MCP can't answer yet.
Three concrete examples
MCP-good — structural navigation:
"Which services call OrderService.CreateOrder?" → grafel_find + grafel_find_callers gives you
the precise call graph with repo context, in one round-trip. grep would require you to know every
caller file location across every repo in the group.
grep-good — raw enumeration:
"List every if err != nil block that is missing a log.Error call." → grep is the right tool.
grafel models control flow at the entity level, not at the statement level. Raw text search on
the source files is faster and more complete for this class of pattern.
Paired — search space reduction then raw verify:
"Does any service leak the internal User.PasswordHash field in an HTTP response?" →
- MCP:
grafel_find entity_type=http_endpoint_definition+grafel_find_pathsto identify every endpoint that touchesUser. Narrows a 500-file repo to 8 handlers. - grep: search only those 8 handler files for
PasswordHashto confirm whether it appears in any serialisation path.
For grafel developer workflow, architecture decisions, and contributing guidelines see
docs/adrs/ and AGENTS.md.
grafel MCP
This repo is part of grafel group grafel. grafel is an architecture knowledge graph available via MCP. When you (an AI coding agent) need to understand how this codebase fits together, prefer the grafel MCP tools over grep + reading files.
When to use grafel instead of grep
| Question shape | Prefer |
|---|---|
"Where is X defined?" |
grafel_find |
"What does X look like + its neighbors?" |
grafel_inspect |
"Who calls X?" |
grafel_expand / grafel_find_callers |
| "End-to-end flow when user does X?" | grafel_traces |
| "How does the frontend talk to the backend?" | grafel_cross_links |
"Show me the source of X" |
grafel_get_source |
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 · 64 lines · 735 tokens per session scan A 60da535f3493
grafel CLAUDE.md is an instructions file published in the GitHub repository cajasmota/grafel (12 stars, last pushed yesterday), licensed MIT. It adds 735 tokens to every session, about $0.0037 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-30.
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.