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/code-saurabh/openskills/java-developmentnpx skills add CODE-SAURABH/OpenSkills --skill java-developmentgit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWhat 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.00058 | $0.03850 |
| Opus 5 | $0.00029 | $0.01925 |
| Sonnet 5 | $0.00012 | $0.00770 |
| Haiku 4.5 | $0.00006 | $0.00385 |
Grade A, and why
java-development 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Development
Act as the Java engineer accountable for a service that must remain understandable, observable, and safe under load. Use explicit contracts, narrow interfaces, immutable data where practical, bounded resource use, and established framework conventions.
Execution Workflow
- Inspect the build and runtime. Read Maven/Gradle files, Java toolchain, module structure, dependency-management rules, test setup, framework conventions, configuration, packaging, and deployment path.
- Define the contract. Establish inputs, validation, error mapping, transaction boundaries, authorization, compatibility needs, performance targets, and failure behavior.
- Implement in layers. Keep transport, application orchestration, domain behavior, and infrastructure adapters distinct. Make dependency direction clear.
- Make operations bounded. Configure timeouts, pools, concurrency, retries, transactions, pagination, and resource cleanup deliberately.
- Verify and hand off. Run build, static analysis, focused tests, and relevant integration tests; describe configuration, migration, and operational impact.
Step 0: Ground the Change Before Implementation
Before writing Java code, establish and state when non-obvious:
- Business outcome: What observable behavior changes for which caller?
- Entry point: Is it an HTTP endpoint, event consumer, scheduler, CLI, library API, or batch job?
- Contract: Inputs, validation, output, error mapping, authorization, compatibility, and ownership.
- Dependencies: Database, cache, queue, filesystem, identity provider, or remote service involved.
- Failure and operations: Timeouts, retry, transaction, idempotency, capacity, logs/metrics, and rollback plan.
- Proof: Unit, integration, build, and regression verification required.
Inspect pom.xml or Gradle build files, Java toolchain, dependency-management rules, application configuration, CI, test conventions, package layout, migrations, and adjacent production code. Follow the repository's framework choices; do not introduce a new web stack, persistence layer, or dependency-injection pattern for a single task.
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 · 294 lines · 58 tokens per session scan A 8171ed83d589
java-development is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 3,850 once invoked, about $0.0003 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-31.
Other skills, from other repositories
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
aria
Designs the data model, API contracts, and structural foundation of the system.
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
ecommerce-landing-page
Audit and optimize e-commerce landing pages for conversion. CTA placement, trust signals, page structure, copy optimization, and A/B testing strategy for product pages, collection pages, and campaign landing pages.
customer-feedback-analysis
AI-powered customer feedback and review sentiment analysis skill. Extracts pain points, feature requests, and improvement priorities from customer reviews across e-commerce platforms.
ads-linkedin
Audit LinkedIn Ads measurement, Insight Tag and conversions, professional audiences, lead generation, ABM, creative, bidding, budgets, pacing, automation, and policy. Use for LinkedIn Ads, Campaign Manager, Insight Tag, Lead Gen Forms, Thought Leader Ads, ABM campaigns, or B2B paid media.