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/jabrena/plinth/024-context-mappingnpx skills add jabrena/plinth --skill 024-context-mappinggit clone --depth 1 https://github.com/jabrena/plinthWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jabrena/plinth/024-context-mapping)<a href="https://agentmods.dev/skills/jabrena/plinth/024-context-mapping"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/024-context-mapping.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00077 | $0.00670 |
| Opus 5 | $0.00039 | $0.00335 |
| Sonnet 5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
024-context-mapping 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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Mapping
Guide identification of Existing systems, Integrations, Ownership, and External dependencies relevant to a problem under exploration. This is an interactive SKILL.
What is covered in this Skill?
- Identifying existing systems that already touch the problem area
- Mapping integrations and data flows between those systems
- Naming ownership: who operates, maintains, or is accountable for each system or integration
- Identifying external dependencies (third-party services, other teams, contracts) outside the team's direct control
- Feeding context-mapping findings into
025-quality-attribute-discoveryand the remaining Functional Specification lenses
Constraints
Map the surrounding context before any design decision assumes a system boundary. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly.
- MUST read
references/024-context-mapping.mdbefore applying Context Mapping guidance - MUST identify existing systems that already touch the problem area, not only the system expected to change
- MUST identify integrations and data flows between the identified systems
- MUST name an owner (team or role) for each identified system or integration when known
- MUST identify external dependencies outside the team's direct control, such as third-party services, other teams, or contracts
- MUST NOT invent a system, integration, owner, or external dependency when the available content is vague or ambiguous; flag the gap for a clarifying question instead
When to use this skill
- Map the systems and integrations around this problem
- Identify ownership for these systems
- List the external dependencies for this issue
- Apply context mapping before design begins
- Draft the Context Mapping section of a Functional Specification
Workflow
- Read the Reference
Read references/024-context-mapping.md, then review the problem frame for systems already implicated by the problem.
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.
- 4d ago First seen · 69 lines · 77 tokens per session scan A 1098d2599356
024-context-mapping is a skill published in the GitHub repository jabrena/plinth (435 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 670 once invoked, about $0.0004 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
design-patterns
Common design patterns with Java examples (Factory, Builder, Strategy, Observer, Decorator, etc.). Use when user asks "implement pattern", "use factory", "strategy pattern", or when designing extensible components.
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
java-migration
Guide for upgrading Java projects between major versions (8→11→17→21→25). Use when user says "upgrade Java", "migrate to Java 25", "update Java version", or when modernizing legacy projects.
jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries). Use when user has JPA performance issues, LazyInitializationException, or asks about entity relationships and fetching strategies.
spring-boot-patterns
Spring Boot best practices and patterns. Use when creating controllers, services or repositories, or when the user asks about Spring Boot layering, wiring, configuration or exception handling. For JPA and Hibernate behaviour, use jpa-patterns instead.
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.