Borrowing it
Nothing to install: this file belongs to onixhdz/cartograph. 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/onixhdz/cartograph/main/AGENTS.mdgit clone --depth 1 https://github.com/onixhdz/cartographWrote 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/onixhdz/cartograph/agents-md)<a href="https://agentmods.dev/instructions/onixhdz/cartograph/agents-md"><img src="https://agentmods.dev/badge/instructions/onixhdz/cartograph/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/onixhdz/cartograph/agents-md"><img src="https://agentmods.dev/badge/instructions/onixhdz/cartograph/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.01039 | $0.01039 |
| Opus 5.5 | $0.00416 | $0.00416 |
| Sonnet 5.5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
cartograph 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 2mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cartograph
Cartograph is local-first code intelligence. Every change should make the tool more accurate, reliable, and useful without adding unnecessary surface area.
Principles
- KISS: Prefer the simplest design that solves the real problem clearly.
- YAGNI: Do not build speculative capabilities, abstractions, or compatibility layers before they are needed.
- Locality of Behavior: Keep related behavior close together so code can be understood without chasing distant indirection.
- Open/Closed: Extend existing seams when appropriate, but do not force abstractions that make simple changes harder.
- Avoid new public surface area unless it is clearly needed. Extend existing concepts before adding commands, flags, endpoints, tools, fields, storage, or graph schema.
- Keep behavior consistent across all supported execution paths. Do not implement CLI-only or mode-specific behavior unless explicitly required.
- Do not expose internal implementation details as user-facing concepts just because they exist in the code.
- Keep everything local by default. Do not introduce external services, network dependencies, or cloud assumptions without an explicit requirement.
- Avoid speculative aliases, compatibility layers, convenience APIs, or migration paths unless there is shipped behavior or persisted data that requires them.
- Check existing local plans before starting substantial feature work. Put new plans or design notes in the local planning area.
Design Discipline
- Spend design effort upfront for non-trivial changes. Simple, durable designs usually require revision, not the first idea.
- Preserve existing graph, storage, API, and UX conventions by inspecting the code before changing them.
- Always explain why when a decision is non-obvious. Rationale helps future maintainers evaluate and preserve intent.
- Solve known correctness, performance, and maintainability risks before shipping changed code.
Safety And Bounds
- Prefer explicit, easy-to-follow control flow over clever branching or hidden behavior.
- Put bounds on work: avoid unbounded loops, queues, goroutines, filesystem walks, graph traversals, and result sets.
- Keep variable scope small. Compute values close to where they are used.
- Handle all errors intentionally with useful context. Do not ignore errors unless the reason is explicit and safe.
- Prefer modern, idiomatic Go with clear errors, minimal abstraction, and no panics outside tests.
- Use assertions or test-only checks for invariants when they make programmer errors fail early.
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.
- 2mo ago First seen · 72 lines · 1,039 tokens per session scan A 71cdaf89072b
cartograph AGENTS.md is an instructions file published in the GitHub repository onixhdz/cartograph (14 stars, last pushed 17d ago), licensed MIT. It adds 1,039 tokens to every session, about $0.0042 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-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).
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.