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/dvnghiem/flowdeck/blast-radius-previewnpx skills add DVNghiem/FlowDeck --skill blast-radius-previewgit 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/blast-radius-preview)<a href="https://agentmods.dev/skills/dvnghiem/flowdeck/blast-radius-preview"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/blast-radius-preview.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.00027 | $0.00481 |
| Opus 5 | $0.00014 | $0.00241 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
blast-radius-preview 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 6d 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
Blast Radius Preview
Before committing to a change, map every system that could break. Activate this skill by providing a change description to the agent.
When to Activate
- Before merging a change that touches shared infrastructure
- Before modifying a public API, event schema, or DB model
- Before changing authentication or session handling
- Any time the Impact Radar returns HIGH
Workflow
- Load the dependency graph from
~/.fd-plan/<slug>/.codebase/MEMORY.json - Start from the directly changed nodes
- Walk the graph outward: find all services/modules that depend on the changed node
- At each hop, check:
- Is this an integration point (API call, event subscription, DB query)?
- Does this path have regression history in
~/.fd-plan/<slug>/.codebase/FAILURES.json? - Is this path covered by integration tests?
- Flag hidden couplings: shared mutable state, ambient context, feature flags
- Produce the blast radius map
Blast Radius Report Format
## Blast Radius Report
### Change
[description]
### Direct Blast (depth 1)
| Module | Coupling Type | Test Coverage | Fragile? |
|--------|--------------|---------------|---------|
### Indirect Blast (depth 2–3)
| Module | Via | Risk Level |
|--------|-----|------------|
### Integration Point Risks
- [endpoint/event]: [why at risk]
### Hidden Couplings
- [module]: shared state / ambient context / feature flag
### Predicted Breakage Categories
- [ ] Performance: [reason]
- [ ] Auth: [reason]
- [ ] Schema: [reason]
- [ ] Async flow: [reason]
### Blast Radius: NARROW | MODERATE | WIDE
Guidance
- NARROW: ≤3 downstream modules, all covered by tests → safe to proceed
- MODERATE: 4–10 downstream modules or ≥1 uncovered → add tests before merging
- WIDE: >10 downstream modules or hits fragile integration → escalate to senior review
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.
- 6d ago First seen · 66 lines · 27 tokens per session scan A 3abf95995fd5
blast-radius-preview is a skill published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 17d ago), licensed MIT. It adds 27 tokens to every session and 481 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.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
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.