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/azalio/map-framework/claude-mdgit clone --depth 1 https://github.com/azalio/map-frameworkWhat 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.01601 | $0.01601 |
| Opus 5 | $0.00800 | $0.00800 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
map-framework 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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAP Framework (mapify-cli) — Agent Instructions
What this repo is
- Purpose:
mapifyis a Python 3.11+ CLI that installs the MAP Framework into a target project (it writes.claude/skill-backed slash surfaces/config and.map/workflow artifacts). - Runtime code:
src/mapify_cli/ - Bundled templates (what users get from
mapify init):src/mapify_cli/templates/ - Dev templates/config used in this repo:
.claude/(keep it in sync withsrc/mapify_cli/templates/)
Critical invariant: template single-source render
All shipped templates are generated from src/mapify_cli/templates_src/**/*.jinja via make render-templates. Never edit the generated trees directly — edit the .jinja source and re-render.
Generated trees (do NOT edit directly):
src/mapify_cli/templates/**.claude/**.codex/**.agents/skills/**
To propagate any change to shipped templates:
make render-templates
Verification:
- Run
make check-render(renders and asserts no diff — enforces generated trees match source). - Run
pytest tests/test_template_render.py -v(byte-identity golden render tests).
Skill catalog invariant
When changing shipped skills, keep .claude/skills/skill-rules.json and src/mapify_cli/templates/skills/skill-rules.json explicit about skillClass:
taskfor manual slash workflows that may call agents, run checks, or write artifacts.referencefor guidance-only skills with no manual invocation, hooks, or runtime effects.hybridonly when reference guidance ships hooks/scripts or artifact side effects; listruntimeEffects.
Validation:
- Run
pytest tests/test_skills.py tests/test_template_render.py -v. - Run
uv run mapify init <new-temp-path> --no-git --mcp noneand inspect generated.claude/skills/skill-rules.jsonfor shipped metadata changes.
How to work in this repo
- Prefer deterministic tooling over “manual review”: run
make check(ormake lint/make test) after changes. - When changing scripts, hooks, CLIs, or generated provider surfaces, test both negative/no-op paths and positive paths with realistic inputs. A hook returning
{}proves only the silent path; also build minimal state/artifacts that should trigger its intended output or side effect. - When changing user-facing behavior, also update relevant docs:
README.md(quick-start)docs/USAGE.md(workflows and CLI usage)docs/ARCHITECTURE.md(system design / agents)
- For releases, follow
RELEASING.mdand updateCHANGELOG.md.
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.
- 2d ago First seen · 132 lines · 1,601 tokens per session scan A 72a09800ad2f
map-framework CLAUDE.md is an instructions file published in the GitHub repository azalio/map-framework (153 stars, last pushed 4d ago), licensed MIT. It adds 1,601 tokens to every session, about $0.0080 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
crewplane AGENTS.md
Instructions for crewplaneai/crewplane, covering agents.md, repo facts, read first, repo map and project heuristics.
agent-orchestrator CLAUDE.md
Claude Code instructions for Untrivial-ai/agent-orchestrator, covering claude.md, app state lives under /.ao only and design system.
superpowers-zh GEMINI.md
Instructions for jnMetaCode/superpowers-zh, covering superpowers-zh 中文增强版, 核心规则, 可用 skills and 如何使用.
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
ai-driven-development AGENTS.md
Instructions for CodeAlive-AI/ai-driven-development, covering ai-driven development — development guide, git publishing defaults, when to create tags and releases, requires a new tag/release and does not require a new tag/release.
mirage CLAUDE.md
Claude Code instructions for strukto-ai/mirage, covering claude.md, repo layout, typescript packages, python/typescript parity and module layout.