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/t1/tdder/mavennpx skills add t1/tdder --skill mavengit clone --depth 1 https://github.com/t1/tdderWrote 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/t1/tdder/maven)<a href="https://agentmods.dev/skills/t1/tdder/maven"><img src="https://agentmods.dev/badge/skills/t1/tdder/maven.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.00055 | $0.01791 |
| Opus 5 | $0.00028 | $0.00896 |
| Sonnet 5 | $0.00011 | $0.00358 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
maven scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
In sandboxed environments the sandbox may block `curl` — tell the user if that happens. How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maven
Shared Maven conventions for all supported agent platforms.
First step — always: read your platform binding before running Maven, suggesting Maven commands, or giving sandbox advice.
Platform Bindings
Read your platform file before doing anything else.
- If
maven_runis in your tool list: readskills/maven/pi.md(relative to the skill checkout) - Otherwise: read
skills/maven/claude.md(relative to the skill checkout)
Your platform file defines the concrete tools, fallback order, and sandbox/network rules. The rest of this file is shared Maven knowledge.
Managing POMs
Dependencies
When adding a new dependency:
- Use the latest stable release version — verify with version lookup (see below)
- Choose the appropriate scope (
compile,provided,runtime,test) and keep them sorted by scope - Prefer managed versions via
<dependencyManagement>in the parent POM
Version properties typically follow the pattern <artifactId.version> or <groupId.version>,
but use whatever is most concise and clear, e.g. assertj.version, cucumber.version, junit.version.
Version Lookup
Always fetch from Maven Central (or another authoritative repository) to verify the latest dependency or plugin version. Never trust version numbers from web search snippets, training data, or other secondary sources.
Use your platform binding's version-lookup tool first.
If that is not available, directly use the Maven repository metadata as a last resort.
DO NOT USE search.maven.org — it's obsolete and returns outdated versions!
Note: repo1.maven.org returns 403 for User-Agents that look like AI or crawlers.
In sandboxed environments the sandbox may block curl — tell the user if that happens.
curl -s -A "Mozilla/5.0" \
"https://repo1.maven.org/maven2/{groupId with . replaced by /}/{artifactId}/maven-metadata.xml"
These XML files contain the list of all versions. You'll have to strip pre-release versions, RC, beta, etc.
Exploring APIs of Dependencies
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 198 lines · 55 tokens per session scan A 4b3551299bec
maven is a skill published in the GitHub repository t1/tdder (14 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 1,791 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
tdd-arrange-act-assert
This skill should be used when the user asks to "structure tests", "organize test code", mentions "arrange act assert", "AAA pattern", "given when then", discusses test readability, or wants to improve test structure.
tdd-red-green-refactor
This skill should be used when the user asks to "do TDD", "write tests first", mentions "red-green-refactor", discusses test-driven development cycles, or wants to build features incrementally with tests.
tdd-test-first
This skill should be used when the user asks to "write tests first", "start with a test", mentions "test-first development", discusses writing tests before implementation, or wants to ensure code is testable by design.
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
specify-incremental
Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.