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 AdamBien/airails --skill java-cli-appgit clone --depth 1 https://github.com/AdamBien/airailsWrote 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/adambien/airails/java-cli-app)<a href="https://agentmods.dev/skills/adambien/airails/java-cli-app"><img src="https://agentmods.dev/badge/skills/adambien/airails/java-cli-app/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/adambien/airails/java-cli-app"><img src="https://agentmods.dev/badge/skills/adambien/airails/java-cli-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 39 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00106 | $0.01237 |
| Opus 5.5 | $0.00042 | $0.00495 |
| Sonnet 5.5 | $0.00021 | $0.00247 |
| Haiku 4.5 | $0.00011 | $0.00124 |
Grade A, and why
java-cli-app 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or maintain a multi-file Java 25 CLI application using $ARGUMENTS. Apply all rules below strictly.
Architecture
- Default: multi-file CLI apps compose with the
/bceskill. The package path follows/bce's[ORGANIZATION].[PROJECT].[BC].[layer]scheme: the organization package (e.g.airhacks) contains the application-level project package (e.g.zbl), whose direct children are the feature business components (BCs);boundary,control,entityonly appear inside a BC, never directly under the application-level package.src/main/java/ Main.java # unnamed package, compact source <organization>/<project>/<bc-a>/{boundary,control,entity}/ <organization>/<project>/<bc-b>/{boundary,control,entity}/ <organization>/<project>/<bc-c>/control/ # BC may have only the layers it needs- Name BCs after their domain responsibilities (e.g.,
auth,users,billing), not technical concerns. - Reserve the application-level package itself for trivial single-class plumbing (e.g. the
Appentry point); anything with business semantics belongs in a BC —/bceowns this rule. - If a design doc or input layout places
boundary/control/entitydirectly under the application-level package, flag it as a BCE violation and propose feature BCs before scaffolding.
- Name BCs after their domain responsibilities (e.g.,
- Exception: small single-purpose tools (one screen of logic, no distinct concerns) — keep everything in one unnamed class with top-level methods, no BCs, no packages.
Build
- For new projects, clone https://github.com/AdamBien/java-cli-app as the project skeleton — it includes the zb build setup and directory structure
- Alternatively, bootstrap from the minimalistic template https://github.com/adambien/z-java-cli-app — a stripped-down starter for fresh
/java-cli-appprojects - Use https://github.com/AdamBien/zb to create executable JARs — no Maven or Gradle required
- Build by running
zb.shin the project root — it compiles all.javafiles fromsrc/main/java/and packages them intozbo/app.jar - Run with
java -jar zbo/app.jar - Offer to generate an executable launcher script with the
/java-cli-scriptskill so the app runs by name instead ofjava -jar zbo/app.jar - Never use
--enable-preview— Java 25 is a GA release, all features used here are standard - Source files use the
.javaextension and live in the project directory
What ships with it
1 file 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.
- 1mo ago Changed · +1 lines ae918d60f990
- 1mo ago First seen · 71 lines · 106 tokens per session scan A 77c72bd4aec5
java-cli-app is a skill published in the GitHub repository AdamBien/airails (58 stars, last pushed 3d ago), licensed MIT. It adds 106 tokens to every session and 1,237 once invoked, about $0.0004 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 skills, from other repositories
authoring-java-sdk-tasks
Writes Airflow task logic in Java, Kotlin, or any JVM language using the Airflow Java SDK. Use when the user wants to implement Airflow tasks in Java/JVM, asks about @Builder.Dag/@Builder.Task/@Builder.XCom, the Task/BundleBuilder interfaces, reading connections/variables/XComs from Java, the JSON-to-Java type…
configuring-airflow-language-sdks
Configures Airflow to run language SDK tasks (Java, Go, and future native SDKs) — register a coordinator, map a queue to it, ensure the runtime/artifact on workers, and tune coordinator options. Use when the user wants Airflow to route a queue to a native-language coordinator, asks about the [sdk]…
aws-sdk-java-v2-bedrock
Provides Amazon Bedrock patterns using AWS SDK for Java 2.x. Invokes foundation models (Claude, Llama, Titan), generates text and images, creates embeddings for RAG, streams real-time responses, and configures Spring Boot integration. Use when asking about Bedrock integration, Java SDK for AI models, AWS generative…
aws-lambda-java-integration
Provides AWS Lambda integration patterns for Java with cold start optimization. Use when deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java approaches, optimizing cold starts below 1 second, configuring API Gateway or ALB integration, or implementing serverless Java applications. Triggers…
langchain4j-ai-services-patterns
Provides patterns to build declarative AI Services with LangChain4j for LLM integration, chatbot development, AI agent implementation, and conversational AI in Java. Generates type-safe AI services using interface-based patterns, annotations, memory management, and tools integration. Use when creating AI-powered Java…
unit-test-parameterized
Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value…