java-cli-app

A skill for creating multi-file Java 25 command-line applications packaged as executable JAR files. A command-line application is a program operated from a terminal, and a JAR is Java's distributable application archive.

In plain words
What is it for?
It is for building or maintaining Java CLI projects with multiple source files, domain-based components, tests, and executable JAR packaging.
Why use it?
It provides project structure and packaging rules so larger Java terminal applications remain organized and runnable without external dependencies.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/adambien/airails/java-cli-app
Any agent
npx skills add AdamBien/airails --skill java-cli-app
Clone the repo
git clone --depth 1 https://github.com/AdamBien/airails

Made for: Claude Code, Codex.

Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,224 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00106 $0.01224
Opus 5 $0.00053 $0.00612
Sonnet 5 $0.00021 $0.00245
Haiku 4.5 $0.00011 $0.00122

Measured yesterday against content hash 77c72bd4aec5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

bce/java-cli-app/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 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 /bce skill. 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, entity only 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 App entry point); anything with business semantics belongs in a BC — /bce owns this rule.
    • If a design doc or input layout places boundary/control/entity directly under the application-level package, flag it as a BCE violation and propose feature BCs before scaffolding.
  • 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-app projects
  • Use https://github.com/AdamBien/zb to create executable JARs — no Maven or Gradle required
  • Build by running zb.sh in the project root — it compiles all .java files from src/main/java/ and packages them into zbo/app.jar
  • Run with java -jar zbo/app.jar
  • Offer to generate an executable launcher script with the /java-cli-script skill so the app runs by name instead of java -jar zbo/app.jar
  • Never use --enable-preview — Java 25 is a GA release, all features used here are standard
  • Source files use the .java extension and live in the project directory

Read the full file on GitHub · 71 lines

Files

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.

Changes

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.

  1. yesterday First seen · 71 lines · 106 tokens per session scan A 77c72bd4aec5

Subscribe to this mod's changes

java-cli-app is a skill published in the GitHub repository AdamBien/airails (47 stars, last pushed 12d ago), licensed MIT. It adds 106 tokens to every session and 1,224 once invoked, about $0.0005 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-08-30.

Related

Other skills, from other repositories

aws-cloudformation-auto-scaling

Provides AWS CloudFormation patterns for Auto Scaling including EC2, ECS, and Lambda. Use when creating Auto Scaling groups, launch configurations, launch templates, scaling policies, lifecycle hooks, and predictive scaling. Covers template structure with Parameters, Outputs, Mappings, Conditions, cross-stack…

giuseppe-trisciuoglio/developer-kit · 74 tokens

aws-cloudformation-bedrock

Provides AWS CloudFormation patterns for Amazon Bedrock resources including agents, knowledge bases, data sources, guardrails, prompts, flows, and inference profiles. Use when creating Bedrock agents with action groups, implementing RAG with knowledge bases, configuring vector stores, setting up content moderation…

giuseppe-trisciuoglio/developer-kit · 81 tokens

aws-cloudformation-cloudfront

Provides AWS CloudFormation patterns for CloudFront distributions, origins (ALB, S3, Lambda@Edge, VPC Origins), CacheBehaviors, Functions, SecurityHeaders, parameters, Outputs and cross-stack references. Use when creating CloudFront distributions with CloudFormation, configuring multiple origins, implementing caching…

giuseppe-trisciuoglio/developer-kit · 81 tokens

aws-cloudformation-cloudwatch

Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability. Use when creating CloudWatch metrics, alarms, dashboards, log groups, log subscriptions, anomaly detection, synthesized canaries, Application Signals, and implementing template structure with…

giuseppe-trisciuoglio/developer-kit · 83 tokens

aws-cloudformation-ecs

Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS…

giuseppe-trisciuoglio/developer-kit · 101 tokens

aws-cloudformation-lambda

Provides AWS CloudFormation patterns for Lambda functions, layers, API Gateway integration, event sources, cold start optimization, monitoring, logging, template validation, and deployment workflows. Use when creating Lambda functions with CloudFormation, configuring event sources, implementing cold start…

giuseppe-trisciuoglio/developer-kit · 70 tokens