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 skills add wolfenazz/YzPzCode --skill codex-interactive-capability-mapgit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWrote 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/wolfenazz/yzpzcode/codex-interactive-capability-map)<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/codex-interactive-capability-map"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/codex-interactive-capability-map/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/codex-interactive-capability-map"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/codex-interactive-capability-map.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.00817 |
| Opus 5.5 | $0.00016 | $0.00327 |
| Sonnet 5.5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
codex-interactive-capability-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 1mo 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.
This is a copy
100% identical to codex-interactive-capability-map — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Interactive Capability Map
Transform a long article, social thread, memo, product essay, or launch narrative into a visual explainer that people can scan and click through.
Use When
- The input is mostly text and the user wants a clearer mental model.
- The content contains repeated concepts, a process, a framework, capabilities, or operating principles.
- The desired output is a polished web artifact, not a static summary.
Workflow
- Read the source material and extract 6-10 core concepts.
- Name the overall model in plain language. Prefer a short noun phrase such as "Operating Model", "Capability Map", or "Workflow Loop".
- Build three linked views:
- A hero that frames the source and the promise.
- A workflow loop that shows the main sequence or system.
- A use-case matrix that combines concepts into practical scenarios.
- Add a right-side detail panel. Clicking any nav item, loop node, matrix card, or maturity level must update the panel.
- Make the clicked element and the detail panel visibly correspond through shared color, motion, icon/mark shape, or gradient.
- Keep copy short. The artifact should reduce reading effort, not recreate the article.
Visual Direction
- Use a Codex-inspired refined product style with soft liquid motion, glassy surfaces, and crisp functional controls.
- Make the first viewport feel like a finished product surface, not a wireframe.
- Favor diagrams, loops, matrices, rails, cards, and progressive disclosure over paragraphs.
- Use meaningful hover and active states. A click should feel consequential.
- Avoid external image dependencies unless the user explicitly provides assets.
Interaction Requirements
- All clickable elements must update content or scroll to a meaningful section.
- The active state must be visually obvious.
- The detail panel should animate on each change.
- Long labels must wrap cleanly and never be clipped.
- The layout must work at 1280px wide and collapse cleanly below 900px.
What ships with it
2 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.
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.
- 1mo ago First seen · 81 lines · 41 tokens per session scan A 686a166aa338
codex-interactive-capability-map is a skill published in the GitHub repository wolfenazz/YzPzCode (20 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 817 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to codex-interactive-capability-map, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
codex-interactive-capability-map
Turn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.
codex-interactive-capability-map
Turn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.
wireframe-prototyping
Creates low-fidelity wireframes and interaction annotations for a feature or screen. Covers user flow identification, ASCII wireframe sketching, interaction annotation, and acceptance criteria. Invoked when the user asks to wireframe a screen, prototype a UI, or sketch a user flow.
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
saas-landing
A single-page SaaS landing page for a software product, with sections such as the hero, features, customer proof, pricing, FAQs, and a call to action. SaaS means software delivered online, usually by subscription.
wireframe-sketch
A hand-drawn wireframe style for exploring page ideas before the final design, using graph paper, rough marks, tabs, notes, and sketch-like charts.