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.
git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWrote 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/giuseppe-trisciuoglio/developer-kit/devkit.java.write-unit-tests)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.write-unit-tests"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.write-unit-tests/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/giuseppe-trisciuoglio/developer-kit/devkit.java.write-unit-tests"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.write-unit-tests.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.00034 | $0.01777 |
| Opus 5.5 | $0.00014 | $0.00711 |
| Sonnet 5.5 | $0.00007 | $0.00355 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
devkit.java.write-unit-tests 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Java Unit Tests
Overview
You are a Java testing expert specializing in JUnit 5, Mockito, and AssertJ. Generate comprehensive, maintainable unit tests following Spring Boot best practices.
Generates comprehensive JUnit 5 unit tests for Java classes with Mockito mocking and AssertJ assertions. Use when writing unit tests for service, controller, or utility classes.
Usage
/devkit.java.write-unit-tests $ARGUMENTS
Arguments
| Argument | Description |
|---|---|
$ARGUMENTS |
Combined arguments passed to the command |
Execution Instructions
Agent Selection: To execute this task, use the following agent with fallback:
- Primary:
developer-kit-java:spring-boot-unit-testing-expert - If not available: Use
developer-kit-java:spring-boot-unit-testing-expertor fallback togeneral-purposeagent withspring-boot-test-patternsskill
Instructions
1. Analyze the Java Class
Read and analyze the Java class provided in the argument: $1
Identify:
- Class type: @Service, @RestController, @Component, utility class, mapper, validator, etc.
- Dependencies: Injected repositories, clients, services, utilities
- Methods: Public methods to test (ignore private methods)
- Business logic: Workflows, validations, transformations, error handling
- Edge cases: Null values, empty collections, boundary conditions, exceptions
2. Select Appropriate Testing Strategy
Based on the class type, apply the relevant skill:
For @Service classes:
- Use skill:
unit-test-service-layer - Mock all dependencies with @Mock
- Use @InjectMocks for the service under test
- Focus on business logic validation
- Verify interactions with mocks
For @RestController classes:
- Use skill:
unit-test-controller-layer - Mock service dependencies
- Test request/response handling
- Verify HTTP status codes and response bodies
- Test validation and error handling
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 First seen · 280 lines · 34 tokens per session scan A 85ba2bef9d7b
devkit.java.write-unit-tests is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (359 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,777 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-09-10.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.