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-integration-tests)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.write-integration-tests"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.write-integration-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-integration-tests"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.write-integration-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.00041 | $0.02719 |
| Opus 5 | $0.00020 | $0.01359 |
| Sonnet 5 | $0.00008 | $0.00544 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
devkit.java.write-integration-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 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Integration Tests for Spring Boot
Overview
Generates comprehensive integration tests for Spring Boot classes using Testcontainers (PostgreSQL, Redis, MongoDB) with
@ServiceConnection pattern. Use when writing integration tests for service or repository classes.
You are tasked with generating a complete integration test for the Java class specified in $1.
Usage
When analyzing the target class, Claude will automatically reference these skills to:
- Determine the appropriate test strategy based on layer (Controller/Service/Repository)
- Select the correct Testcontainers based on dependencies
- Apply framework-specific testing patterns
- Generate comprehensive test scenarios covering all edge cases
- Use
@MockitoBeanfor mocking dependencies (replaces deprecated@MockBean)
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
Process
1. Analyze Target Class
- Read the class file from
$1 - Identify the layer (Controller, Service, Repository)
- Detect dependencies (Database, Cache, Message Queue, etc.)
- Identify external integrations
2. Determine Required Testcontainers
Based on dependencies, include:
- PostgreSQL: For JPA repositories or database operations
- Redis: For caching or session management
- MongoDB: For NoSQL operations
- RabbitMQ/Kafka: For messaging operations
- Additional containers: Based on specific dependencies
3. Generate Integration Test
Follow these patterns from the spring-boot-test-patterns skill:
Test Structure
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 · 387 lines · 41 tokens per session scan A 78197dc9797d
devkit.java.write-integration-tests is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (344 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,719 once invoked, about $0.0002 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-09-10.
Other commands, from other repositories
create-backend-tests
Command "create-backend-tests" from codeready-toolchain/tarsy, covering writing tests for go backend, running tests, from project root, direct go commands and critical rules.
run-e2e
Run end-to-end tests against the application using Playwright or Cypress.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.