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 DVNghiem/FlowDeck --skill change-impact-radargit clone --depth 1 https://github.com/DVNghiem/FlowDeckWrote 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/dvnghiem/flowdeck/change-impact-radar)<a href="https://agentmods.dev/skills/dvnghiem/flowdeck/change-impact-radar"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/change-impact-radar/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/dvnghiem/flowdeck/change-impact-radar"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/change-impact-radar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00433 |
| Opus 5 | $0.00015 | $0.00217 |
| Sonnet 5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
change-impact-radar 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 9d 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
Change Impact Radar
Predicts blast surface before the AI touches a single file. Activate this skill by providing the intended change description to the agent.
When to Activate
Activate before:
- Any multi-file refactor
- API contract changes
- Schema migrations
- Dependency upgrades
- Auth / security changes
Workflow
- Read
~/.fd-plan/<slug>/.codebase/ARCHITECTURE.mdand~/.fd-plan/<slug>/.codebase/STACK.mdfor system context - Read
~/.fd-plan/<slug>/.codebase/MEMORY.jsonto trace the module dependency graph - From the change description, identify all directly affected files
- Walk the dependency graph outward from affected files (depth ≤ 3 hops)
- Identify test files that cover the affected modules
- Flag any database schema, API contracts, or config changes
- Produce the impact map report
Impact Map Report Format
## Change Impact Report
### Direct Impact (files you will edit)
| File | Type | Risk |
|------|------|------|
### Indirect Impact (dependents, ≤3 hops)
| File | Dependency Chain | Risk |
|------|-----------------|------|
### API Contracts at Risk
- [contract name]: [why at risk]
### Tests to Run / Update
- [test file]: covers [module]
### Database / Config paths
- [path]: [what changes]
### Volatility Warnings
- [file]: marked as [stability level]
### Verdict: LOW | MEDIUM | HIGH impact
Guidance
- If MEMORY.json does not exist, run
/fd-task— its init step builds the graph. - If a file has no test coverage and is indirectly impacted, flag it as "coverage gap".
- Never proceed with a HIGH impact change without human confirmation.
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.
- 9d ago First seen · 63 lines · 29 tokens per session scan A 05f8038fffdb
change-impact-radar is a skill published in the GitHub repository DVNghiem/FlowDeck (25 stars, last pushed 20d ago), licensed MIT. It adds 29 tokens to every session and 433 once invoked, about $0.0001 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-30.
Other skills, from other repositories
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.