cartography

Document code execution flows and map source files into cartography markdown.

63|8|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/JoranHonig/grimoire --skill cartography-joranhonig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cartography
Source: https://github.com/JoranHonig/grimoire/tree/main/skills/cartography
Command: npx skills add https://github.com/JoranHonig/grimoire --skill cartography-joranhonig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Security researchers and code auditors repeatedly spend time re-discovering the same execution paths (authentication, data pipelines, permission checks) each time they revisit a codebase. This Skill captures lightweight, navigable flow maps that document where to look so agents and humans can rebuild context in seconds instead of re-exploring the repository.

Core Features & Use Cases

  • Index and Discover: Run an index over stored cartography files and surface existing flows that match the investigator's query.
  • Seeded and Unseeded Exploration: Follow a callgraph from provided entry points or deploy a swarm of subagents to discover candidate files, then refine into a linear flow sequence.
  • Author Cartography Files: Create slugified cartography files with YAML frontmatter, entry points, key components, flow sequences, security notes, and conditional sections for optional sub-flows.
  • Use Case: Trace an authentication flow across services, document entry points and trust boundaries, and save a cartography file so future audits load precise context instantly.

Quick Start

Ask cartography to map the authentication flow starting from gateway/src/middleware/auth.ts.

Frequently Asked Questions about cartography

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document code execution flows for quick context rebuilding?

Document code execution flows by mapping relevant source files and callgraphs into lightweight cartography markdown files with YAML frontmatter, entry points, key components, and flow sequences for fast agent-driven context rebuilds.

What is the best way to trace authentication flows across services during security research?

Tracing authentication flows across services involves following the callgraph from provided entry points or deploying subagents to discover candidate files, then refining them into a linear, navigable flow sequence saved as a cartography file.

Can I map code flows without providing specific entry points?

Yes, you can map permission and data pipeline flows without specific entry points by deploying an unseeded swarm of subagents to discover candidate files, which are then refined into a linear flow sequence for your audit.

Does cartography work for code auditing scenarios involving trust boundaries and conditional sub-flows?

Cartography works for code auditing by documenting entry points, trust boundaries, and security notes, while including conditional sections for optional sub-flows to capture complex execution paths across services.

How do I find existing flow maps for a codebase I am revisiting?

Find existing flow maps by running an index over stored cartography files, which surfaces previously documented execution paths that match your current investigation query for immediate context loading.