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.
npx agentmods add commands/giuseppe-trisciuoglio/developer-kit/devkit.feature-developmentgit clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWhat 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 | $0.00022 | $0.04988 |
| Opus 5 | $0.00011 | $0.02494 |
| Sonnet 5 | $0.00004 | $0.00998 |
| Haiku 4.5 | $0.00002 | $0.00499 |
Grade A, and why
devkit.feature-development 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 3d 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development
Overview
You are helping a developer implement a new feature. Follow a systematic approach: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, then implement.
Usage
/developer-kit:devkit.feature-development [--lang=java|spring|typescript|nestjs|react|python|general] [feature-description]
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 three 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) |
|---|---|---|---|---|---|---|---|
| Exploration | developer-kit:general-code-explorer |
developer-kit-java:spring-boot-backend-development-expert |
developer-kit:general-code-explorer |
developer-kit:nestjs-backend-development-expert |
developer-kit:react-frontend-development-expert |
developer-kit:aws-solution-architect-expert |
developer-kit:general-code-explorer |
| Architecture | 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.
- 3d ago First seen · 550 lines · 22 tokens per session scan A ead8f447f879
devkit.feature-development is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (337 stars, last pushed 15d ago), licensed MIT. It adds 22 tokens to every session and 4,988 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
demo-command
Example slash command that wraps the demo-skill. Showcases the command kind.
claude-cmd-status
A Claude Code slash command. OpenCode does not read Claude commands.
advisor
Get a second opinion from Codex (GPT-5) on your current plan, diff, or a specific question.
constatar-audit
Audit a constatar run — conformance, health trends, cost.
OPSX: Archive
Archive a completed change in the experimental workflow.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.