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.fix-debugging)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.fix-debugging"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.fix-debugging/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.fix-debugging"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.fix-debugging.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.00024 | $0.04271 |
| Opus 5.5 | $0.00010 | $0.01708 |
| Sonnet 5.5 | $0.00005 | $0.00854 |
| Haiku 4.5 | $0.00002 | $0.00427 |
Grade A, and why
devkit.fix-debugging 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 2mo 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix & Debugging
Overview
You are helping a developer fix a bug or debug an issue. Follow a systematic approach: understand the problem, trace the root cause, design a minimal fix, then implement and verify.
Usage
/developer-kit:devkit.fix-debugging [--lang=java|spring|typescript|nestjs|react|python|general] [issue-description or error-message]
Arguments
| Argument | Description |
|---|---|
$ARGUMENTS |
Combined arguments passed to the command |
Current Context
The command will automatically gather context information when needed:
- Current git branch and status
- Recent commits and changes
- Available when the repository has history
Execution Instructions
Agent Selection: Based on the --lang parameter, select the appropriate agents:
Integration with Sub-agents
This command leverages specialized sub-agents using the Task tool.
Language/Framework Selection
Parse $ARGUMENTS to detect the optional --lang parameter:
--lang=springor--lang=java: Use Java/Spring Boot specialized agents--lang=typescriptor--lang=ts: Use TypeScript specialized agents--lang=nestjs: Use NestJS specialized agents--lang=react: Use React frontend specialized agents--lang=aws: Use AWS specialized agents (architecture, CloudFormation, IaC)--lang=pythonor--lang=py: Use Python specialized agents--lang=generalor no flag: Use general-purpose agents (default)
Agent Mapping by Language:
| Phase | General (default) | Java/Spring Boot (--lang=spring or --lang=java) |
TypeScript (--lang=typescript or --lang=ts) |
NestJS (--lang=nestjs) |
React (--lang=react) |
AWS (--lang=aws) |
Python (--lang=python or --lang=py) |
|---|---|---|---|---|---|---|---|
| Debugger | developer-kit:general-debugger |
developer-kit:general-debugger |
developer-kit:general-debugger |
developer-kit:general-debugger |
developer-kit:general-debugger |
developer-kit:general-debugger |
developer-kit:general-debugger |
| Architect | developer-kit:general-software-architect |
developer-kit-java:java-software-architect-review |
developer-kit-typescript:typescript-software-architect-review |
developer-kit-typescript:typescript-software-architect-review |
developer-kit-typescript:react-software-architect-review |
developer-kit-aws:aws-solution-architect-expert |
developer-kit-python:python-software-architect-expert |
| Code Review | developer-kit:general-code-reviewer |
developer-kit-java:spring-boot-code-review-expert |
developer-kit-typescript:general-code-reviewer |
developer-kit-typescript:nestjs-code-review-expert |
developer-kit-typescript:general-code-reviewer |
developer-kit-aws:aws-architecture-review-expert |
developer-kit-python:python-code-review-expert |
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.
- 2mo ago First seen · 499 lines · 24 tokens per session scan A 0b92a10191ea
devkit.fix-debugging is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (366 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 4,271 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-08-30.
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.