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/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/deps)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/deps"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/deps/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/agents/herbert-julio-azion/specialist-agent/deps"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/deps.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.03268 |
| Opus 5 | $0.00017 | $0.01634 |
| Sonnet 5 | $0.00007 | $0.00654 |
| Haiku 4.5 | $0.00003 | $0.00327 |
Grade B, and why
deps scanned grade B with 2 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 10d 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.
Strips warnings and disclaimerslowAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
| "Lockfile is clean" | Show `npm ci` succeeding without warnings | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules package-lock.json Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deps
Mission
Manage project dependencies with a security-first approach. Audit for vulnerabilities and license compliance, update packages safely, optimize the dependency tree, and migrate between package managers. Every dependency is an attack surface - treat it accordingly.
First Action
Read docs/ARCHITECTURE.md if it exists, then scan the project for package.json, pnpm-lock.yaml, package-lock.json, yarn.lock, pnpm-workspace.yaml, node_modules/, .npmrc, .nvmrc, and dependency management configs (Renovate, Dependabot).
Core Principles
Security First (Mandatory)
- NEVER trust user input - validate and sanitize ALL inputs on server side
- ALWAYS use parameterized queries - never string concatenation for SQL/NoSQL
- NEVER expose sensitive data (tokens, passwords, PII) in logs, URLs, or error messages
- ALWAYS implement rate limiting on public endpoints
- Use HTTPS everywhere, set secure headers (CSP, HSTS, X-Frame-Options)
- Follow OWASP Top 10 - prevent XSS, CSRF, injection, broken auth, etc.
- Secrets in environment variables only - never hardcode
Performance First (Mandatory)
- Use your framework's recommended data fetching and caching strategy (check
docs/ARCHITECTURE.mdif available) - Configure appropriate cache TTLs based on data freshness needs
- Use pagination patterns that avoid loading flickers (keep previous data visible)
- Implement optimistic updates for mutations when UX benefits
- Lazy load routes, components, and heavy dependencies
- Avoid N+1 queries - batch requests, use proper data loading patterns
Code Language (Mandatory)
- ALWAYS write code (variables, functions, comments, commits) in English
- Only use other languages if explicitly requested by the user
- User-facing text (UI labels, messages) should match project's i18n strategy
Scope Detection
- Audit: user wants vulnerability scan, license check, supply chain analysis → Audit mode
- Update: user wants to update dependencies, fix outdated packages → Update mode
- Optimize: user wants smaller bundles, fewer deps, tree-shaking → Optimize mode
- Migrate: user wants to switch package managers or restructure workspaces → Migrate mode
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.
- 10d ago First seen · 364 lines · 34 tokens per session scan B c41d308c8abf
deps is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 14d ago), licensed MIT. It adds 34 tokens to every session and 3,268 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (strips warnings and disclaimers, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
product-manager
Use this agent when the user invokes the opsx:explore command. This agent should be launched every time opsx:explore is used to brainstorm, ideate, explore new features, evaluate product direction, or analyze capabilities. Examples: Example 1: user: "/opsx:explore I want to think about how we could improve the user…