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 Kaddo-kdd/kaddo --skill legacy-risk-assessmentgit clone --depth 1 https://github.com/Kaddo-kdd/kaddoWrote 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/kaddo-kdd/kaddo/legacy-risk-assessment)<a href="https://agentmods.dev/skills/kaddo-kdd/kaddo/legacy-risk-assessment"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/legacy-risk-assessment/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/kaddo-kdd/kaddo/legacy-risk-assessment"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/legacy-risk-assessment.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.00065 | $0.00664 |
| Opus 5.5 | $0.00026 | $0.00266 |
| Sonnet 5.5 | $0.00013 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
legacy-risk-assessment 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 28d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy Risk Assessment Skill
Purpose
Evaluate a planned change against known legacy risks, unknowns and modernization candidates to identify which findings require additional consideration before or after implementation.
When to use
Before or during implementation of a Work Item in a legacy project — especially when the
Work Item touches areas flagged in knowledge/legacy/risks.md.
Inputs
- The Work Item (id, ACs, affected_modules, affected areas).
knowledge/legacy/risks.md— known risks with RISK-xxx identifiers.knowledge/legacy/unknowns.md— known unknowns with UNK-xxx identifiers.knowledge/legacy/modernization-candidates.md— MOD-xxx candidates.- System Graph (
.kaddo/graph.json) when available. - Implementation Handoff or Implementation Evidence when available.
Output
A risk assessment report listing which legacy findings are relevant to the planned change, their intersection with the affected areas, and recommended actions.
Output template
# Legacy Risk Assessment — <WI id>
## Relevant Risks
### RISK-xxx: <title>
- **Intersection:** <how this risk relates to the planned change>
- **Action:** mitigate before | monitor during | verify after | not applicable
- **Notes:** <additional context>
## Relevant Unknowns
### UNK-xxx: <question>
- **Impact on this WI:** <how this unknown affects implementation>
- **Recommended:** investigate before | accept as assumption | defer
## Relevant Modernization Candidates
### MOD-xxx: <title>
- **Alignment:** <how this WI relates to the modernization target>
- **Recommendation:** advance | defer | not relevant
## Summary
- Risks requiring pre-implementation mitigation: <count>
- Unknowns requiring investigation: <count>
- Modernization candidates advanced by this WI: <count>
- Overall risk posture: low | medium | high
Rules
- Reference findings by their stable identifiers — do not copy full content.
- Assess intersection based on affected areas (file paths, modules, system entities).
- Not every legacy finding is relevant — filter to those that intersect the change.
- Do not block implementation solely because legacy risks exist — provide context for informed decision-making.
- When the System Graph is available, use entity relationships to discover indirect risk intersections.
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.
- 28d ago First seen · 83 lines · 65 tokens per session scan A 169d4cba1ed6
legacy-risk-assessment is a skill published in the GitHub repository Kaddo-kdd/kaddo (67 stars, last pushed 13d ago), licensed MIT. It adds 65 tokens to every session and 664 once invoked, about $0.0003 per session on Opus 5.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-09-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…