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 skills/soulcodex/agentic/project-mapnpx skills add soulcodex/agentic --skill project-mapgit clone --depth 1 https://github.com/soulcodex/agenticWhat 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.00049 | $0.00898 |
| Opus 5 | $0.00024 | $0.00449 |
| Sonnet 5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
project-map 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Map Skill
Generate .agentic/project-map.md to orient any agent to the codebase.
Step 0 — Check Existing Map
Check if .agentic/project-map.md already exists:
- If present: Ask the user if they want to refresh it or keep existing.
- Default: keep existing unless
--refreshflag is passed or user explicitly requests refresh.
- Default: keep existing unless
- If absent: Continue to Step 1.
Step 1 — Auto-discover Codebase Structure
Detect the language and architecture by inspecting the filesystem:
-
Detect language(s) — inspect for manifest files:
go.mod→ Gopackage.json/tsconfig.json→ TypeScript/JavaScriptpyproject.toml→ Pythoncomposer.json→ PHP
-
Detect architecture markers — inspect directory names:
- Hexagonal:
domain/,application/,infrastructure/,ports/ - CQRS:
command/,query/ - DDD: aggregate roots, value objects, domain events
- Hexagonal:
-
Read build/test/lint commands — inspect:
Makefilejustfilepackage.json scriptsTaskfile.yml
-
Identify entry points — look for:
main.gocmd/src/index.tsapp/main.pyartisanbin/
-
For monorepos — detect tier structure from
.agentic/config.yamlif present.
Step 2 — Map the Layer Structure
-
Identify architectural layers:
- Domain: entities, value objects, domain events, repository interfaces
- Application: use cases, command/query handlers
- Infrastructure: repository implementations, HTTP clients, messaging adapters
- Ports/Adapters: HTTP controllers, CLI commands, message consumers
-
List key modules/packages (top 5-10) with one-line purpose each.
-
Note non-obvious conventions:
- Naming rules (e.g.,
*_test.gosuffix,service.gopatterns) - File organization (co-location rules, split by concern vs. feature)
- Error handling patterns
- Token/entity naming conventions
- Naming rules (e.g.,
Step 3 — Identify Complexity Hotspots
- Largest files by line count — use
wc -lor equivalent on key source files.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 107 lines · 49 tokens per session scan A 0748ce817c89
project-map is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 898 once invoked, about $0.0002 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-31.
Other skills, from other repositories
help
Use when asked what the capstone plugin can do - prints the usage block.
explain-codebase
Drop into any repo and generate a structured architecture overview. Maps the codebase, identifies entry points, frameworks, and dependencies — then produces a "start here" guide for new contributors.
core
Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.
feature
Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom -> plan -> implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline…
groom
Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature…
map
Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on…