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.architect-review)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.architect-review"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.architect-review/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.architect-review"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.architect-review.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.00029 | $0.01119 |
| Opus 5.5 | $0.00012 | $0.00448 |
| Sonnet 5.5 | $0.00006 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
devkit.java.architect-review 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Architectural Review
Overview
Validates Java application architecture focusing on Clean Architecture, DDD, and Spring Boot patterns. Use when reviewing architectural decisions or before major refactoring. Perform a comprehensive architectural review of a Java application, focusing on Clean Architecture principles, Domain-Driven Design patterns, and Spring Boot best practices.
Usage
/devkit.java.architect-review $ARGUMENTS
Arguments
| Argument | Description |
|---|---|
$ARGUMENTS |
Combined arguments passed to the command |
Execution Instructions
Agent Selection: To execute this architectural review, use the following agent with fallback:
- Primary:
java-software-architect-review - If not available: Use
developer-kit:java-software-architect-reviewor fallback togeneral-purposeagent withspring-boot-crud-patternsskill
Context
- Project structure: !
find . -name "*.java" -type f | head -20 - Build system: !
ls -la | grep -E "(pom\.xml|build\.gradle|build\.gradle\.kts)" - Package structure: !
find . -name "*.java" -type f | grep -E "src/main/java" | head -10 - Spring Boot configuration: !
find . -name "application*.yml" -o -name "application*.properties"
Review Focus Areas
$1 specifies the package path to review (optional - defaults to entire codebase):
- Examples: "com.example.users", "src/main/java/com/example/users", "users/"
$2 specifies the focus area (optional):
clean-architecture- Clean Architecture layer separationddd- Domain-Driven Design patternsspring-boot- Spring Boot specific patternssecurity- Security architectureperformance- Performance and scalabilitytesting- Test architecturemicroservices- Microservices architectureall- Complete architectural review (default)
Architectural Review Checklist
Clean Architecture Assessment
- Layer Separation: Verify proper dependency direction (domain � application � infrastructure � presentation)
- Package Structure: Feature-based organization with clear boundaries
- Dependency Rules: Check for violations of dependency inversion principle
- Domain Purity: Ensure domain layer has no framework dependencies
- Interface Segregation: Clean API design between layers
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 · 143 lines · 29 tokens per session scan A 5a2c7b50721f
devkit.java.architect-review is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (360 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,119 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.