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.generate-refactoring-tasks)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.generate-refactoring-tasks"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.generate-refactoring-tasks/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.generate-refactoring-tasks"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.generate-refactoring-tasks.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.00951 |
| Opus 5.5 | $0.00014 | $0.00380 |
| Sonnet 5.5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
devkit.java.generate-refactoring-tasks 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring Task List Generator for Bounded Context
Overview
Generates a comprehensive refactoring task list for a specific Bounded Context in project and saves it to a file. Use when planning refactoring work for a bounded context.
Usage
/devkit.java.generate-refactoring-tasks $ARGUMENTS
Arguments
| Argument | Description |
|---|---|
$ARGUMENTS |
Combined arguments passed to the command |
Execution Steps
Analyze the bounded context $1 in the project to create a complete refactoring task list and save it to a file.
Perform the following steps:
-
Bounded Context Analysis:
- Search for all Java files in the package
$1 - Identify all TODO, FIXME comments, and technical debt indicators
- Analyze DDD architecture and compliance with SOLID principles
- Identify incomplete implementations and placeholder code
- Search for all Java files in the package
-
Map the Structure:
- List all found files by layer (domain, application, infrastructure, presentation)
- Identify dependencies between components
- Analyze entities, aggregates, value objects, services, repositories, controllers
- Detect architectural patterns and violations
-
Generate Organized Task List: Create a task list with this exact structure:
# $1 Bounded Context Refactoring Tasks > Generated on: 2025-11-24 ## Overview List of refactoring activities to be performed in the $1 bounded context... ## Current State - **Identified TODOs**: [number] refactoring/clean comments - **Missing Documentation**: [number] classes without Javadoc - **Incomplete Implementations**: [number] methods with placeholders - **Unused Methods**: [number] methods to remove ## Task List ### Priority 1: Documentation and Critical Functionality #### 1.1 Complete Javadoc Documentation [List of checkboxes for each file with TODO javadoc] #### 1.2 Implement Incomplete Functionality [List of checkboxes for each placeholder method to implement] #### 1.3 Remove Unused Code [List of checkboxes for each unused method to remove] ### Priority 2: Domain Model Enhancement [Tasks to improve domain model, value objects, aggregates] ### Priority 3: Architecture Improvements [Tasks to improve architecture, ports, interfaces] ### Priority 4: Infrastructure Cleanup [Tasks for database cleanup, configuration, imports] ## Execution Notes ### Task Dependencies [Logical dependencies between priorities] ### Time Estimate [Days estimate for each priority] ### Validation Checklist for each Task [Standard validation criteria]
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 · 132 lines · 34 tokens per session scan A 610459b9a398
devkit.java.generate-refactoring-tasks is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (360 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 951 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.