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/jl-cmd/claude-dev-env/shownpx skills add jl-cmd/claude-dev-env --skill showgit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWhat 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.00066 | $0.00484 |
| Opus 5 | $0.00033 | $0.00242 |
| Sonnet 5 | $0.00013 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
show 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 3d 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.
What it actually says
Show
Use this skill when a user asks to show, draw, map, visualize, explain visually, or build an interactive visual.
Routes
Pick the row whose intent matches the request, then follow workflows/create-visual.md.
| Intent | Route |
|---|---|
| Steps, decisions, lifecycle, transformation | flowchart |
| Architecture, containment, hierarchy | structural |
| Mechanism, intuition, spatial metaphor | illustrative |
| Entity or class relationships | erd |
| Controls that change a visual explanation | interactive |
| UI surface, form, card, dashboard | mockup |
| Quantitative or geographic data | chart |
| Illustration or generative art | art |
Each route's references and template live in routing.yaml; the template sets the output type.
Invariants
- Design, palette, and color meaning follow
references/core-design.md. - SVG output follows
references/svg-contract.md; HTML output followsreferences/host-and-html.md. - Prefer multiple focused visuals over one dense canvas, and keep explanatory prose outside the visual.
- Keep one diagram family per visual.
- When the visual shows code, a diff, or a plan that lives in a repo, read the real lines and tie every arrow to a
path:linecitation before drawing. When the picture and the source disagree, the picture is wrong. samples/holds good examples the user has picked out. Read them on demand to study what works; the rules stay in the references.
Workflows
- New visual:
workflows/create-visual.md - Review or repair:
workflows/review-visual.md
Validation
Run from any working directory:
python <skill-root>/scripts/validate-package.py
python <skill-root>/scripts/validate-artifact.py <artifact>
The package is complete only when package checks, artifact checks, and rendered inspection all pass.
What ships with it
33 files 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.
- references/accessibility.md 461 B
- references/art.md 197 B
- references/charts.md 212 B
- references/core-design.md 1.3 KB
- references/erds.md 181 B
- references/flowcharts.md 248 B
- references/host-and-html.md 273 B
- references/illustrative-diagrams.md 919 B
- references/interaction.md 239 B
- references/mockups.md 174 B
- references/quality-gates.md 386 B
- references/structural-diagrams.md 204 B
- references/subject-inventory.md 590 B
- references/svg-contract.md 1.2 KB
- routing.yaml 1.2 KB
- samples/pr1262-v2.svg 19 KB
- scripts/README.md 264 B
- scripts/validate-artifact.py 4.7 KB runs code
- scripts/validate-package.py 770 B runs code
- templates/html-widget.html 167 B
- templates/svg-base.svg 1006 B
- tests/fixtures/css-var.svg 383 B
- tests/fixtures/dead-ref.svg 418 B
- tests/fixtures/filled-glyph.svg 329 B
- tests/fixtures/inherited-fill.svg 925 B
- tests/fixtures/invalid.svg 70 B
- tests/fixtures/large-canvas.svg 1.2 KB
- tests/fixtures/unfilled-connector.svg 691 B
- tests/fixtures/valid.html 80 B
- tests/test_validate-artifact.py 2.4 KB runs code
- tests/test_validators.py 2.2 KB runs code
- workflows/create-visual.md 615 B
- workflows/review-visual.md 1.1 KB
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.
- 3d ago First seen · 52 lines · 66 tokens per session scan A d416b4f37502
show is a skill published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 484 once invoked, about $0.0003 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
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…