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 hmcts/agentic-plugins-marketplace --skill dependency-auditgit clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplaceWrote 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/hmcts/agentic-plugins-marketplace/dependency-audit)<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/dependency-audit"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/dependency-audit/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/hmcts/agentic-plugins-marketplace/dependency-audit"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/dependency-audit.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.00031 | $0.00912 |
| Opus 5.5 | $0.00012 | $0.00365 |
| Sonnet 5.5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
dependency-audit 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 1mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Scans CP repositories for dependency version inconsistencies, outdated libraries, and parent POM alignment issues.
When to Use
- User asks to "check dependency versions", "audit dependencies", "find version mismatches"
- User wants to verify a specific library version across all repos
- User wants to check parent POM chain alignment
- Before upgrading a shared library to find all consumers
Process
Step 1: Determine Scope
Ask the user what to audit:
- All context services — scan all
cpp-context-*repos - Specific repos — scan named repositories
- Specific dependency — find all usages of a named dependency
- Parent POM chain — verify super-pom → parent-pom → service alignment
Step 2: Extract Version Information
For Maven repos (cpp-context-*, cp-*)
Read pom.xml from each repo root and extract:
- Parent POM —
<parent>groupId, artifactId, version - Properties —
<properties>block for version properties - Direct dependencies — any
<dependency>with explicit versions (not managed) - Plugin versions — any plugins with explicit versions
Key properties to check across the parent POM chain:
| Property | Defined in | Controls |
|---|---|---|
cpp.framework.version |
Service POM | cp-framework-libraries version |
cpp.microservice-framework.version |
Service POM | cp-microservice-framework version |
cpp.event-store.version |
Service POM | cp-event-store version |
cpp.file-service.version |
Service POM | cp-file-service version |
cpp.platform-libraries.version |
Service POM | cpp-platform-libraries version |
For Gradle repos (cp-audit-*, cp-auth-*, cpp-mbd-*)
Read build.gradle and extract:
- Plugin versions — Spring Boot, dependency-management
- Dependencies — implementation, testImplementation blocks
- Ext properties — version variables
For Node repos (cpp-ui-*)
Read package.json and extract:
- Angular version —
@angular/core - Key dependencies — ngrx, govuk-frontend, ngx-bootstrap
- Node/npm versions — engines field or .nvmrc
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.
- 1mo ago First seen · 106 lines · 31 tokens per session scan A 15a8f14ef792
dependency-audit is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (4 stars, last pushed 11d ago), licensed MIT. It adds 31 tokens to every session and 912 once invoked, about $0.0001 per session on Opus 5.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
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
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"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…