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 orcasecurity/orca-skills --skill orca-impact-analysisgit clone --depth 1 https://github.com/orcasecurity/orca-skillsWrote 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/orcasecurity/orca-skills/orca-impact-analysis)<a href="https://agentmods.dev/skills/orcasecurity/orca-skills/orca-impact-analysis"><img src="https://agentmods.dev/badge/skills/orcasecurity/orca-skills/orca-impact-analysis/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/orcasecurity/orca-skills/orca-impact-analysis"><img src="https://agentmods.dev/badge/skills/orcasecurity/orca-skills/orca-impact-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 542 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00079 | $0.07749 |
| Opus 5 | $0.00039 | $0.03875 |
| Sonnet 5 | $0.00016 | $0.01550 |
| Haiku 4.5 | $0.00008 | $0.00775 |
Grade A, and why
orca-impact-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 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.
How it starts
The opening of the file, as written. The whole thing — 724 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orca Impact Analysis Skill
Answers two questions:
- "If I fix this, what else closes?" — alerts, attack paths, compliance controls resolved
- "If I fix this, what might break?" — production workflows, automation, and services that depend on the current (insecure) state
Given a single Orca alert, this skill analyzes BOTH sides of remediation impact — the security improvements AND the operational risk of applying the fix.
Usage
/orca-impact-analysis <alert-id>
/orca-impact-analysis orca-3380725
Or natural language:
- "what's the impact of fixing orca-3380725?"
- "if I fix orca-3511464, what else closes?"
- "impact analysis for orca-3213766"
- "what does remediation of orca-3380725 resolve?"
What This Skill Does
- Fetches the alert and identifies the root cause and fix action
- Queries same-asset alerts to find co-located findings that share the same root cause
- Queries attack paths to find kill chains that break when this alert is fixed
- Queries similar alert type across the environment to find the same issue on other assets
- Checks compliance impact to find frameworks/controls that would pass after the fix
- Simulates breakage risk using CloudTrail/CDR events, effective permissions, and usage patterns to identify production workflows that depend on the current state
- Synthesizes a full impact report with security gains AND operational risks
Processing Logic
Step 1: Understand the Fix
Fetch the alert with get_alert and determine:
- What is the root cause? (e.g., missing MFA, exposed service, overprivileged role)
- What is the fix action? (e.g., enable MFA, add authentication, remove role assignment)
- What asset is affected? (asset type, ID, account, cloud provider)
Categorize the fix type:
Fix Type Examples Cascade Pattern
─────────────────────────────────────────────────────────────────────
Configuration fix Enable MFA, restrict access Closes same-asset alerts that depend on this config
Permission fix Remove role, tighten policy Breaks attack paths, closes privilege escalation chains
Exposure fix Add auth, block port, restrict IP Closes exposure alerts, breaks external attack paths
Patch/update Apply CVE patch, upgrade version Closes all CVE alerts for that package version
Removal Delete unused resource Closes ALL alerts on that asset
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 · 724 lines · 79 tokens per session scan A c7fe6120230f
orca-impact-analysis is a skill published in the GitHub repository orcasecurity/orca-skills (49 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 7,749 once invoked, about $0.0004 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
ml-pipeline-workflow
Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (npx netlify). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.
public-web-deploy
Publish a public website safely: DNS, web server, HTTPS, hardening, verify. Routes raw dev servers through nginx/Caddy/Apache/Cloudflare Pages.
game-pipeline
Game lifecycle orchestrator: scaffold, assets, audio, QA, deploy.
service-health-check
Service health monitoring, endpoint validation, and CVE source auditing.
docker-devops
Docker/K8s: Dockerfile, multi-stage, compose, manifests, Helm. Triggers: Docker, Dockerfile, container, Kubernetes, k8s, compose, Helm, pod.