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/motlin/claude-code-plugins/pom-orderingnpx skills add motlin/claude-code-plugins --skill pom-orderinggit clone --depth 1 https://github.com/motlin/claude-code-pluginsWrote 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/motlin/claude-code-plugins/pom-ordering)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/pom-ordering"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/pom-ordering.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.00024 | $0.00619 |
| Opus 5 | $0.00012 | $0.00309 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
pom-ordering 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 yesterday.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ordering Rules
First, group dependencies by scope (compile, runtime, test).
Within each scope, group by groupId in this order:
- First-party (${project.groupId} or modules within the project)
- cool.klass
- io.liftwizard
- org.eclipse.collections
- io.dropwizard
- Other third-party libraries
- Jakarta
Region Comment Structure
Use region comments for each groupId+scope combination:
<!--region Project compile dependencies --><!--region Project runtime dependencies --><!--region Klass compile dependencies --><!--region Klass runtime dependencies --><!--region Liftwizard compile dependencies --><!--region Liftwizard runtime dependencies --><!--region Compile dependencies -->(for other dependencies)<!--region Runtime dependencies --><!--region Test dependencies -->
Close each region with <!--endregion [name] -->
Within some groups, use nested regions for further organization:
- For io.liftwizard runtime:
<!--region Liftwizard bundles -->then<!--region Liftwizard config--> - For io.dropwizard: core modules first, then specialized modules
Example Structure
<dependencies>
<!--region Project compile dependencies -->
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>example-services</artifactId>
<version>${project.version}</version>
</dependency>
<!--endregion-->
<!--region Project runtime dependencies -->
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>example-domain-model</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
</dependency>
<!--endregion-->
<!--region Liftwizard runtime dependencies -->
<dependency>
<groupId>io.liftwizard</groupId>
<artifactId>liftwizard-graphql-reladomo-meta</artifactId>
<scope>runtime</scope>
</dependency>
<!--region Liftwizard bundles -->
<dependency>
<groupId>io.liftwizard</groupId>
<artifactId>liftwizard-bundle-cors</artifactId>
<scope>runtime</scope>
</dependency>
<!--endregion-->
<!--region Liftwizard config-->
<dependency>
<groupId>io.liftwizard</groupId>
<artifactId>liftwizard-config-logging-logstash-console</artifactId>
<scope>runtime</scope>
</dependency>
<!--endregion-->
<!--endregion-->
<!--region Test dependencies -->
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter</artifactId>
<scope>test</scope>
</dependency>
<!--endregion-->
</dependencies>
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.
- yesterday First seen · 97 lines · 24 tokens per session scan A a223b237c6cc
pom-ordering is a skill published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 619 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-09-04.
Other skills, from other repositories
azure-security-keyvault-secrets-java
Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.
azure-ai-anomalydetector-java
Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.
azure-communication-chat-java
Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.
azure-communication-common-java
Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.
union-type-wrappers
Add typed getters and setters over BinaryData properties that represent TypeSpec union types in generated Java models. Use when generated classes expose BinaryData for union-typed fields and you need ergonomic, type-safe accessors instead.
azure-ai-agents-persistent-java
Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".