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 agents/me2resh/apexyard/dependency-auditorgit clone --depth 1 https://github.com/me2resh/apexyardWhat 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.00026 | $0.01294 |
| Opus 5 | $0.00013 | $0.00647 |
| Sonnet 5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
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 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Auditor Agent
Persona name: Munir
Type: Automated agent
Trigger: Weekly, or when package.json changes
Purpose
Monitor dependencies for vulnerabilities, outdated packages, and license compliance.
Relationship to /audit-deps and the CI pipeline: this agent, the /audit-deps skill, and golden-paths/pipelines/dependency-audit.yml cover the same ground from three angles — the skill is the operator-invoked on-demand run, the pipeline is the scheduled CI enforcement, and this agent is the reasoning/triage layer that interprets their output (CVE triage, license disposition, upgrade recommendations). Keep the three consistent; the skill and pipeline are the source of truth for what is scanned.
Trigger Conditions
Run an audit when:
- A weekly scheduled scan fires (typically Mondays)
package.jsonorpackage-lock.jsonis modified- A new project is added
- A manual trigger is requested
Audit Process
1. Identify all projects with package.json
2. Run npm audit on each
3. Check for outdated packages
4. Verify license compliance
5. Generate consolidated report
6. Create tickets for issues
7. Notify relevant teams
Audit Checks
1. Vulnerability Scan
npm audit --json > audit-results.json
Group results by severity (critical, high, moderate, low — npm audit's output vocabulary; moderate maps to Medium in reports, matching the Head of Security response table) and identify affected packages and paths.
Action by severity:
| Severity | Action |
|---|---|
| Critical | Immediate ticket, block deploys |
| High | Ticket this week |
| Medium | Ticket this sprint |
| Low | Track in backlog |
2. Outdated Packages
npm outdated --json > outdated.json
Categories:
- Major version behind — review breaking changes
- Minor version behind — schedule update
- Patch behind — update ASAP (usually fixes)
3. License Compliance
Allowed licences:
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 · 197 lines · 26 tokens per session scan A a29c38512df0
dependency-auditor is an agent published in the GitHub repository me2resh/apexyard (497 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 1,294 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.