Borrowing it
Nothing to install: this file belongs to adamw7/tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adamw7/tools/main/.claude/commands/module-build.mdgit clone --depth 1 https://github.com/adamw7/toolsWrote 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/commands/adamw7/tools/module-build)<a href="https://agentmods.dev/commands/adamw7/tools/module-build"><img src="https://agentmods.dev/badge/commands/adamw7/tools/module-build/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/commands/adamw7/tools/module-build"><img src="https://agentmods.dev/badge/commands/adamw7/tools/module-build.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.00015 | $0.00531 |
| Opus 5.5 | $0.00006 | $0.00212 |
| Sonnet 5.5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
module-build 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.
What it actually says
Build the module named in $ARGUMENTS, at the lifecycle phase it names (default
install).
mvn -pl <module> -am <phase>
-pl is always paired with -am. Without it the build fails before
compiling anything: the root pom's ReactorModuleConvergence rule rejects a
reactor whose modules' parents are absent from it, and sibling -SNAPSHOTs such
as mcp-common do not resolve from the local repository until they are
installed. If you see a missing parent or an unresolved sibling, that is this
mistake and not the module's code. Asked for test on data, run package
instead: data requires mcp-common by the automatic module name its jar
carries, and a test-only reactor never builds that jar, so the compile fails
with module not found: tools.mcp.common.
Resolve the module name against the root pom's <modules> before running
anything. Two are worth knowing:
codeis an aggregator; its real modules arecode/protogen-maven-plugin,code/protogen-maven-plugin-testandcode/context.data-testis deliberately outside the root reactor, so it is built from its own directory rather than with-pl.
If the request is really one test rather than a module, use one of these instead
— -Dtest applies to every module in the reactor, so surefire fails the upstream
ones where nothing matches:
cd <module> && mvn test -Dtest='SomeTest#someMethod'
mvn -pl <module> -am package -Dtest=SomeTest -Dsurefire.failIfNoSpecifiedTests=false
The first form needs mvn install -DskipTests to have run once, since a module
directory resolves its siblings from the local repository rather than the
reactor.
Add clean when the change removed a code-generation source, so a stale
generated builder in target/ cannot mask it.
Report the verdict and, on a failure, the module and test that failed with the assertion message — not the reactor summary.
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 Changed · +3 lines dd0c6931f6a5
- 1mo ago First seen · 47 lines · 15 tokens per session scan A 64688fcbebce
module-build is a command published in the GitHub repository adamw7/tools (11 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 531 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-30.
Other commands, from other repositories
benchmark
Design and coordinate a reproducible Java performance test.
index
High-performance web crawling engine with bindings for 11 languages.
justfile-recipe-short-doc
Shorten justfile recipe doc comments for simple recipes.
test
Run /test — see .claude/commands/test.md for the authoritative spec.
generate-and-verify
Trigger annotation processing in the demo module to generate all outputs (DTOs, MCP tools, REST controllers, OpenAPI spec), then verify the generated code compiles and matches expected patterns. List all generated files with a summary of what each contains.
java-build
Build Java project with Maven or Gradle - compile, test, package.