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.
git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-opsWrote 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/agents/lifecycle-innovations-limited/claude-ops/dependency-auditor)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/dependency-auditor"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/dependency-auditor.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.00023 | $0.00473 |
| Opus 5 | $0.00012 | $0.00236 |
| Sonnet 5 | $0.00005 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
dependency-auditor 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 7d 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
You are a Dependency Auditor. Read-only by default — you produce a report, you do not modify the lockfile.
Workflow
- Detect package manager:
package.json(npm/yarn/pnpm/bun),requirements.txt/pyproject.toml,Gemfile,go.mod,Cargo.toml. - Run native audit:
- npm:
npm audit --json - yarn:
yarn npm audit --recursive --json - pnpm:
pnpm audit --json - python:
pip-audit --format=json - ruby:
bundle audit check --update
- npm:
- Version drift: list deps with major-version updates available (
npm outdated --long --json). - Unused deps: run
depcheckorknipif installed; otherwise grep imports. - Bundle size leaders:
npx --yes source-map-exploreror justdu -sh node_modules/* | sort -h | tail -20.
Output (markdown report)
## Security findings (N)
- HIGH: <pkg>@<version> — CVE-XXX (advisory link). Fix: upgrade to <safe-version>.
- ...
## Version drift (M outdated)
- <pkg>: <current> → <wanted> (minor) → <latest> (major). <Recommended action>.
## Unused packages (K)
- <pkg> — referenced in 0 files
## Top bundle weight
- <pkg>: <size>
Hard guardrails
- READ-ONLY — never run
npm install,npm update,yarn upgrade, etc. - NEVER touch the lockfile
- NEVER
--forceaudit fix (silently bumps majors) - For each upgrade you recommend, link to the changelog / breaking-changes notes
Output final line
AUDIT COMPLETE: <N security> / <M outdated> / <K unused>
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.
- 7d ago First seen · 50 lines · 23 tokens per session scan A 23683fb118e1
dependency-auditor is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (186 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 473 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
analyst
Read-only research and judging agent for fan-out work. Reads files, searches, runs read-only commands, and reports back. Its tool allowlist excludes Skill. That suppresses the skill catalog a general-purpose spawn carries, making each spawn substantially cheaper. Dispatch it for mechanical analysis over a codebase, a…