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/marcoemrich/exact-coding-exercises/example-mappingnpx skills add marcoemrich/EXACT-Coding-Exercises --skill example-mappinggit clone --depth 1 https://github.com/marcoemrich/EXACT-Coding-ExercisesWhat 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.00080 | $0.03094 |
| Opus 5 | $0.00040 | $0.01547 |
| Sonnet 5 | $0.00016 | $0.00619 |
| Haiku 4.5 | $0.00008 | $0.00309 |
Grade A, and why
example-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 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example Mapping
Conduct an interactive Example Mapping session with the user.
What is Example Mapping?
Example Mapping (by Matt Wynne) is a collaborative technique to explore a feature BEFORE implementation. It uses these categories of cards to structure the discovery:
- Story (yellow): The feature or user story being explored
- Rules (blue): Business rules and acceptance criteria discovered during discussion
- Examples (green): Concrete examples that illustrate a rule - these become tests later
- Questions (red): Open questions and uncertainties that need clarification
- New Stories: Behavior discovered during the session that belongs to a DIFFERENT story - sliced out of the current scope rather than explored here
Why Example Mapping Before TDD?
Example Mapping is the bridge between requirements and test lists:
- Example Mapping discovers rules and concrete examples through conversation
- Test List (
/test-list) converts those examples intoit.todo()test cases - Red-Green-Refactor implements them one by one
Without Example Mapping, developers often:
- Miss important business rules
- Start coding before understanding the domain
- Write tests for the wrong things
- Discover edge cases too late
How to Conduct the Session
Session Context: This is an INTERVIEW, not a group workshop
Example Mapping was designed for the Three Amigos around a table. This command runs a different format: a 1:1 interview between you and a single domain expert. That difference changes how you handle open questions.
In the original group workshop, open questions get parked on a red card and the session moves on. The reason is social: stopping to research would stall three or more people, and the person who could answer is usually not in the room.
In this interview, the person who can answer IS in the room - that's the entire point of the format. So the default is inverted: ask immediately instead of parking. A question you park here is a question you could have resolved in ten seconds.
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 · 273 lines · 80 tokens per session scan A 2646c7f512b2
example-mapping is a skill published in the GitHub repository marcoemrich/EXACT-Coding-Exercises (13 stars, last pushed 13d ago), licensed MIT. It adds 80 tokens to every session and 3,094 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…