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/serac-labs/serac/blast-radiusnpx skills add serac-labs/serac --skill blast-radiusgit clone --depth 1 https://github.com/serac-labs/seracWrote 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/serac-labs/serac/blast-radius)<a href="https://agentmods.dev/skills/serac-labs/serac/blast-radius"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/blast-radius.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.00039 | $0.02911 |
| Opus 5 | $0.00019 | $0.01456 |
| Sonnet 5 | $0.00008 | $0.00582 |
| Haiku 4.5 | $0.00004 | $0.00291 |
Grade A, and why
blast-radius 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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blast Radius for ServiceNow
Blast Radius provides configuration dependency analysis across a ServiceNow instance. Before making changes to fields, tables, or artifacts, use these tools to understand the full blast radius.
Tool Overview
| Tool | Purpose | When to Use |
|---|---|---|
snow_blast_radius_apps |
List apps with config counts | Starting point — understand the instance landscape |
snow_blast_radius_table_configs |
All configs on a table | "What runs on the incident table?" |
snow_blast_radius_field_references |
Reverse field lookup | "What touches incident.assignment_group?" |
snow_blast_radius_artifact_dependencies |
Forward dependency analysis | "What does this business rule read/write?" |
snow_blast_radius_dependents |
Find what uses / calls an artifact (deep 3-phase scan, 100+ tables) | "What calls IncidentUtils?" / "Can I safely delete this business rule?" |
snow_code_search |
Substring search across every script-bearing table (business rules, script includes, client scripts, widgets, scripted REST ops, UI actions, ACLs, notifications, UX scripts, …) | "Where is IncidentUtils.resolve referenced anywhere?" — use when reverse-dependency tools don't index what you need |
Coverage
snow_blast_radius_field_references and snow_blast_radius_table_configs scan the following artifact types in parallel. Types backed by plugins that are not activated on the instance fail silently — the tool reports them under errors_by_type and continues.
Table-scoped (queried with the table name as filter):
- Business rules (
sys_script) — script + condition + filter_condition + role_conditions - Client scripts (
sys_script_client) - UI actions (
sys_ui_action) — script + condition - UI policies (
sys_ui_policy) — script_true + script_false + conditions - UI policy actions (
sys_ui_policy_action) — exact field match - Data policies (
sys_data_policy2) - Data policy rules (
sys_data_policy_rule) — exact table_field match - ACLs (
sys_security_acl) — field-level name match always included, table-level only when script/condition references the field - Email notifications (
sysevent_email_action) — subject + message_html + message_text + condition + advanced_condition - Metric definitions (
metric_definition) — script + exact field match - Inbound email actions (
sysevent_in_email_action) — script + condition - Transform entries (
sys_transform_entry) — target_field / source_field - Dictionary
dependent/dependent_on_field— UI-level field dependencies
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 · 226 lines · 39 tokens per session scan A c4356eb64a2e
blast-radius is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 11d ago), licensed Apache-2.0. It adds 39 tokens to every session and 2,911 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-30.
Other skills, from other repositories
triage
Diagnose and fix broken MCP servers in mcptoon — doctor, health, per-server probes, and the common failure playbook.
debugging
Systematic debugging protocol for finding and fixing bugs. Activates for "debug", "fix bug", "not working", "error", "broken", "issue", "fails", "crash", "undefined", "null" problems. Hardened against 169 sessions of real-world friction data.
test-driven-fix
Test-first debugging loop that reproduces bugs with failing tests, then iterates until tests pass. Activates for "write a test first", "test-driven fix", "TDD fix", "reproduce with test", "make it pass", or when fixing bugs that have an existing test suite.
bug
A map of this repo's bug-intake triage — three buckets a defect falls into, and which one is worth a read-only root-cause investigation before any patch gets written. Not a new pipeline; a reminder to classify before coding, and a guard against a symptom-patch that hides a live defect. Reach for it when a bug report…
qa
QA test a live website with Axon discovery/content evidence plus browser automation when interaction is required. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.
engineering-robustness
Reference for designing, changing, debugging, testing, and releasing AI-generated code so failures become durable regression assets and completion is proven across the real delivery boundary.