map-framework CLAUDE.md

Development instructions for mapify, a Python command-line tool that installs the MAP Framework and its workflow files into another project.

In plain words
What is it for?
Use them when changing templates, framework skills, configuration, or the commands that render and check shipped files.
Why use it?
They explain which template files are the source and how to regenerate and verify the generated copies without losing consistency.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/azalio/map-framework/claude-md
Clone the repo
git clone --depth 1 https://github.com/azalio/map-framework
Per session 1,601 This file is loaded in full into every session.
When invoked 1,601 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 72a09800ad2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

CLAUDE.md · 132 lines

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: mapify is 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 with src/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:

  • task for manual slash workflows that may call agents, run checks, or write artifacts.
  • reference for guidance-only skills with no manual invocation, hooks, or runtime effects.
  • hybrid only when reference guidance ships hooks/scripts or artifact side effects; list runtimeEffects.

Validation:

  • Run pytest tests/test_skills.py tests/test_template_render.py -v.
  • Run uv run mapify init <new-temp-path> --no-git --mcp none and inspect generated .claude/skills/skill-rules.json for shipped metadata changes.

How to work in this repo

  • Prefer deterministic tooling over “manual review”: run make check (or make 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.md and update CHANGELOG.md.

Read the full file on GitHub · 132 lines

Changes

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.

  1. 2d ago First seen · 132 lines · 1,601 tokens per session scan A 72a09800ad2f

Subscribe to this mod's changes

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.