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/arnosdeus/agent-toolkit/dependency-reviewnpx skills add Arnosdeus/agent-toolkit --skill dependency-reviewgit clone --depth 1 https://github.com/Arnosdeus/agent-toolkitWrote 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/arnosdeus/agent-toolkit/dependency-review)<a href="https://agentmods.dev/skills/arnosdeus/agent-toolkit/dependency-review"><img src="https://agentmods.dev/badge/skills/arnosdeus/agent-toolkit/dependency-review.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 | $0.00028 | $0.00145 |
| Opus 5 | $0.00014 | $0.00072 |
| Sonnet 5 | $0.00006 | $0.00029 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
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.
What it actually says
Dependency Review
Procedure and output
Compare manifests and lockfiles, inspect usage, and check advisories and
licenses where available. Report BLOCKER, MAJOR, MINOR, or NOTE findings
with package/version evidence and remediation; never silently edit dependencies.
Inspect manifests and lockfiles for outdated, unused, duplicate, incompatible, or vulnerable packages; lockfile consistency; licensing concerns where detectable; and transitive risk. Do not upgrade automatically unless requested. Verify package provenance and explain the impact of each recommendation.
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 First seen · 18 lines · 28 tokens per session scan A 640b9445b43a
dependency-review is a skill published in the GitHub repository Arnosdeus/agent-toolkit (2 stars, last pushed 10d ago), licensed MIT. It adds 28 tokens to every session and 145 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-31.
Other skills, from other repositories
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
release-cli
Release a new version of the tokenmaxxing CLI to npm. Use when explicitly asked to release or publish @851-labs/tokenmaxxing, including checking main, bumping apps/cli/package.json, updating CHANGELOG.md, committing, tagging cli-vX.Y.Z, pushing, monitoring generated native package publishing, and smoke testing the…
first-plan-co-change-analysis
Skill que constrói o Co-change Graph - "quando arquivo X muda, qual outro arquivo geralmente muda junto?". Use durante Discovery e em /fp:cochange. Baseado em git history. Detecta arquivos co-dependentes que devem ser editados juntos para evitar PRs incompletos. v0.3.0+ usa engine nativo Rust quando disponível…
first-plan-provenance-tracker
Skill que define o schema de proveniência e o sistema de freshness tracking para findings em .first-plan/. Use durante Discovery e refresh para registrar source (file:line@SHA), TTL, confidence inicial e cadeia de supersedeção. Aplica decay de confidence baseado em idade.
first-plan-reconciliation
Skill que define Spec-Code Reconciliation - matching contínuo entre artefatos de intenção (docs, specs, JIRA, GitHub issues) e implementação (código, testes, PRs). Use durante Discovery e em /fp:check para identificar feature ja implementada, em flight, drifted ou abandonada.
first-plan-semantic-reuse
Skill que faz busca semantica via BM25 sobre o indice de simbolos do projeto. Substitui grep do reuse-index quando o engine nativo esta disponivel. Encontra "preciso de validacao de email" mesmo se a funcao se chama validateEmailRFC. Use durante /fp:reuse e /fp:plan para identificar componentes reusaveis com matching…