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 equinor/fusion-skills --skill fusion-dependency-reviewgit clone --depth 1 https://github.com/equinor/fusion-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/equinor/fusion-skills/fusion-dependency-review)<a href="https://agentmods.dev/skills/equinor/fusion-skills/fusion-dependency-review"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-dependency-review/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/equinor/fusion-skills/fusion-dependency-review"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-dependency-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00097 | $0.01998 |
| Opus 5 | $0.00048 | $0.00999 |
| Sonnet 5 | $0.00019 | $0.00400 |
| Haiku 4.5 | $0.00010 | $0.00200 |
Grade A, and why
fusion-dependency-review 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 3d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Review
Structured review workflow for dependency update PRs. Produces consistent research notes that incorporate existing PR discussion, multi-lens analysis, and an actionable verdict with explicit maintainer confirmation before any merge action.
When to use
Use when a dependency PR needs review and you want a consistent, auditable decision process.
Typical triggers:
- "Review this dependency PR"
- "Should we merge this dependency update?"
- "Check this Renovate/Dependabot PR"
- "Review one of our open dependency PRs"
- "What changed in this library bump?"
- "Is this dependency update safe to merge?"
- PR title contains dependency update patterns (e.g.
chore(deps):,fix(deps):,bump,update) - User shares a PR URL for a dependency update
When not to use
- Feature PRs or application code reviews (use standard code review workflows)
- Dependency automation or bot configuration
- Approving/merging without explicit user confirmation
- Deciding organizational dependency policy
Required inputs
Collect before starting:
- Repository owner and name
- PR number or URL, or a copied PR summary including package name, version change, changed files, and CI status
- Optional: specific review concerns or areas of focus
If required details are missing, ask concise clarifying questions from references/questions.md.
If PR target is missing or ambiguous:
- Ask only the minimal follow-up question needed to identify the target PR.
- When repository context is known, use GitHub MCP to list likely open dependency PRs and let user choose.
- Keep shortlist concise: include PR number, title, dependency/package hint, author, and CI state when available.
Auto-extract from the PR when available:
- Package(s) being updated and version range (from → to)
- Changelog/release notes URL
- CI status
- Changed files and dependency ecosystem
- Existing top-level PR comments, review comments, and unresolved thread state
Instructions
Preferred advisor orchestration
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/code-quality-advisor.md 2.1 KB
- agents/impact-advisor.md 2.0 KB
- agents/research-advisor.md 3.3 KB
- agents/security-advisor.md 2.2 KB
- agents/source-control-advisor.md 3.8 KB
- agents/target-pr-advisor.md 2.3 KB
- agents/verdict-advisor.md 3.9 KB
- assets/research-template.md 2.3 KB
- assets/review-tracker.md 3.6 KB
- assets/verdict-template.md 2.8 KB
- CHANGELOG.md 4.1 KB
- references/instructions.md 5.9 KB
- references/questions.md 1.2 KB
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.
- 3d ago Changed · +3 lines cba0c195d060
- 11d ago First seen · 172 lines · 97 tokens per session scan A ebc4eb156a08
fusion-dependency-review is a skill published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 97 tokens to every session and 1,998 once invoked, about $0.0005 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…