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/sembraniteam/claude-plugins/impact-matrixnpx skills add sembraniteam/claude-plugins --skill impact-matrixgit clone --depth 1 https://github.com/sembraniteam/claude-pluginsWrote 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/sembraniteam/claude-plugins/impact-matrix)<a href="https://agentmods.dev/skills/sembraniteam/claude-plugins/impact-matrix"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/impact-matrix.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.00134 | $0.01146 |
| Opus 5 | $0.00067 | $0.00573 |
| Sonnet 5 | $0.00027 | $0.00229 |
| Haiku 4.5 | $0.00013 | $0.00115 |
Grade A, and why
impact-matrix 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impact Matrix
Complexity × Impact Prioritization Matrix
Scoring Dimensions
Score each finding on two dimensions (1–3 scale):
Impact — user or business effect if fixed
| Score | Meaning |
|---|---|
| 3 | Directly visible to users or causes SLO breach |
| 2 | Measurable improvement but not directly user-facing |
| 1 | Minor improvement; internal or technical benefit only |
Complexity — effort required to implement the fix
| Score | Meaning |
|---|---|
| 1 | <1 day: config change, add index, fix cache header |
| 2 | 1–5 days: refactor one component, add cache layer, pool objects |
| 3 | >1 sprint: architectural change, data model migration, platform upgrade |
Priority score = Impact ÷ Complexity (higher = act sooner)
Quadrant Map
HIGH IMPACT (3)
│
Quick Wins │ Strategic Projects
Impact 3 │ Impact 3
Complexity 1│ Complexity 3
────────────┼────────────────────
LOW │ HIGH
COMPLEXITY │ COMPLEXITY
────────────┼────────────────────
Low-Hanging │ Avoid / Defer
Fruit │ Impact 1
Impact 1-2 │ Complexity 3
Complexity 1│
│
LOW IMPACT (1)
- Quick Wins → Ship immediately; highest ROI
- Strategic Projects → Schedule in roadmap; break into milestones
- Low-Hanging Fruit → Batch in a cleanup sprint
- Avoid / Defer → Do not prioritize; revisit if scale or impact changes
Scoring Template
When given a list of findings, produce this prioritized table:
| # | Finding | Impact | Complexity | Score | Quadrant |
|---|--------------------------------|--------|------------|-------|-------------------|
| 1 | Add index on orders.user_id | 3 | 1 | 3.0 | Quick Win |
| 2 | Migrate to async I/O | 3 | 3 | 1.0 | Strategic Project |
| 3 | Enable gzip on API responses | 2 | 1 | 2.0 | Low-Hanging Fruit |
| 4 | Rewrite ORM to raw SQL | 1 | 3 | 0.3 | Avoid / Defer |
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 · 104 lines · 134 tokens per session scan A dd91e513f9bb
impact-matrix is a skill published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 1,146 once invoked, about $0.0007 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…