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/monkilabs/opencastle/context-mapnpx skills add monkilabs/opencastle --skill context-mapgit clone --depth 1 https://github.com/monkilabs/opencastleWhat 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.00041 | $0.00555 |
| Opus 5 | $0.00020 | $0.00278 |
| Sonnet 5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
context-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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Context Map
Generate file impact map before code changes to identify affected files, relationships, cascades — improves agent file partitions for parallel work.
When to Use
| Use | Skip |
|---|---|
| Feature implementation (Phase 1) | Isolated bug fixes ≤2 files |
| Refactoring (Phase 1 Scope) | |
| Schema changes cascading through queries/components | |
Any task touching libs/ |
Steps
1 — Entry Points
Identify files that MUST change from task description.
2 — Trace Outward (dependents)
Find consumers of entry-point exports:
rg -n "import .*from .*libs/auth" # find importers
rg -n "\bAuthCard\b" --type ts --type tsx # find component consumers
rg -n "auth.*route|/auth" # find route references
If the assistant exposes a code-usage lookup (find-references), prefer it for symbols: it resolves re-exports and aliases that a text search misses.
3 — Trace Inward (sources)
Find what entry points depend on:
rg -n "from .*libs/" src/auth/ # shared lib deps
rg -n "from .*config" src/auth/ # config deps
4 — Build the Map
Produce a compact map for Team Lead and downstream agents:
Context Map — Feature: Add priceRange
- Entry points:
- src/lib/place/schema.ts
- src/components/PriceRangeFilter/PriceRangeFilter.tsx
- Dependents (trace outward):
- src/pages/places/page.tsx
- src/components/PlacesList/PlaceCard.tsx
- Sources (trace inward):
- src/lib/filters.ts
- src/shared/types/place.ts
- Unaffected (optional):
- src/components/Account/**
Validation checkpoint: every search hit lands in the map; all listed files open without errors (typecheck via the codebase-tool slot). Full template, depth levels, partition derivation, Team Lead integration: see REFERENCE.md.
Anti-Patterns
- Skipping for "obvious" tasks — shared libs cascade unexpectedly
- Guessing dependencies instead of searching for them
- Over-mapping a 2-file fix
- Using a stale map after plan changes
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 · 72 lines · 41 tokens per session scan A 4a8501816518
context-map is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 555 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-30.
Other skills, from other repositories
product-architect
Complete product development system with 64 agents and 35 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
codex-delegation
Use when a coding task would benefit from delegating work to Codex in the background — a deep independent second opinion, security or architecture analysis, or a parallel implementation running while the session continues. Lets Claude drive the codex companion itself (task, review, status --wait, result) without the…
cursor-delegation
Use when a coding task would benefit from delegating work to Cursor in the background — fast parallel implementation, scaffolding, or an everyday review running while the session continues. Lets Claude drive the cursor companion itself (task, review, status --wait, result) without the user typing /cursor: commands.
cursor-cli-runtime
Internal helper contract for calling the cursor-companion runtime from Claude Code.
cursor-prompting
Internal guidance for composing cursor-agent prompts and picking models for coding, review, diagnosis, and research tasks inside the Cursor Claude Code plugin.
cursor-result-handling
Internal guidance for presenting Cursor helper output back to the user.