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/joinwell52-ai/codeflowmu-open/eval-risk-gap-analysisnpx skills add joinwell52-AI/CodeFlowMu-open --skill eval-risk-gap-analysisgit clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-openWrote 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/joinwell52-ai/codeflowmu-open/eval-risk-gap-analysis)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/eval-risk-gap-analysis"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/eval-risk-gap-analysis.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.1 | $0.00040 | $0.00186 |
| Opus 5 | $0.00020 | $0.00093 |
| Sonnet 5 | $0.00008 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
eval-risk-gap-analysis 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 5d 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
EVAL Risk and Gap Analysis
When to use
Use when an observation needs severity and owner classification.
Rules
- Compare expected and actual behavior.
- Classify risk type.
- Recommend P0/P1/P2 with reason.
- Keep recommendation separate from ADMIN decision.
Required output
Use docs/skills/eval-playbook/risk-gap-analysis.md.
Forbidden actions
- Do not create public issues automatically.
- Do not confuse local gaps with formal protocol gaps.
- Do not decide governance outcome.
Minimal example
Risk type: docs
Severity: P2
Owner: DEV
Reason: discoverability issue, not runtime blocker
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.
- 5d ago First seen · 37 lines · 40 tokens per session scan A 68ae04489c35
eval-risk-gap-analysis is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 11d ago), licensed MIT. It adds 40 tokens to every session and 186 once invoked, about $0.0002 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
Skill "systematic-debugging" from jnMetaCode/superpowers-zh, covering 系统化调试, 概述, 铁律, 何时使用 and 四个阶段.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
ha-logs
Self-service diagnostics — query Hope Agent's local SQLite databases (logs / sessions / background jobs) directly via the exec tool to investigate problems, analyze usage, and locate root causes. Trigger on: user reports something broken / failing / slow / stuck / not responding ('X 不工作', 'X 报错', 'X 卡住', '为什么 X 失败'…
grepai
Semantic code search and call-graph tracing. Use for intent questions ('where is authentication handled?'), exploring unfamiliar code, or tracing callers/callees — as a ranking layer on top of exact-match Grep, not a replacement for it.
macos-test-triage
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…