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/loiane/specs-driven-development-spring-angularWrote 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/loiane/specs-driven-development-spring-angular/code-simplify)<a href="https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/code-simplify"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/code-simplify/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/loiane/specs-driven-development-spring-angular/code-simplify"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/code-simplify.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.00023 | $0.00539 |
| Opus 5.5 | $0.00009 | $0.00216 |
| Sonnet 5.5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
code-simplify 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.
What it actually says
/code-simplify
Phase: 6 (meta) — clarity sweep
Owning agent: .claude/agents/spring-code-reviewer.md
Skills used: clarity-over-cleverness, tdd-red-green-refactor
Purpose
Apply the clarity-over-cleverness rules to a single file or a directory while keeping tests green. This is the same pass /build's simplify phase performs, but on demand.
Inputs
<path>(positional). A file undersrc/main/**or a directory.- Optional
--dry-runto print proposed edits without writing.
Reads
<path>(the target file/directory)..claude/skills/clarity-over-cleverness/SKILL.md(authoritative checklist).
Writes
- The targeted files (in place).
- A diff summary appended to
.specs/<feature-id>/05-implementation-log.mdunder a### simplify-passblock, or to a freshclarity-pass-<date>.mdif no active feature.
Process
- Refuse if
mvn testis not green right now (run it first; abort on failure). - For each file in scope, apply the 7 rewrite targets in order:
- Untangle nested ternaries → if/else.
- Streams only when clearer than a loop; otherwise loop.
- Inline once-used helpers.
- Kill option flags (split into two methods).
- Name domain concepts (no
data,info,manager,helper,util). - Remove premature abstraction (interface with one impl, factory with one product).
- Prefer early returns over deep nesting.
- Re-run
mvn testafter each file. If anything goes red, revert that file's edits and record it as a Skipped item. - Emit a summary: files touched, rewrites applied per category, tests run, regressions encountered.
Refuse if
- Tests are not green at start.
- The path is under
src/test/**(test clarity is governed by/test, not this command).
Done when
All in-scope files are either simplified or explicitly skipped, and tests are green.
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 · 46 lines · 23 tokens per session scan A a5a326db0309
code-simplify is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 19d ago), licensed MIT. It adds 23 tokens to every session and 539 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
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
devkit.java.code-review
Validates Java code quality for enterprise Spring applications with security, performance, architecture and best practices analysis. Use when reviewing code changes or before merging pull requests.
sddp-qc
Command description: Run quality control against the implemented feature. Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync] Command category: feature-delivery Prerequisites: spec, plan, tasks, implementation:complete.
util.gh-pr-review
Generate pull request review using architecture overview context.
review.speckit-code
Review the implementation against the entire spec-driven development documentation set (including the constitution) for compliance; detect and explain drift among code↔spec↔plan↔tasks - provide prioritised, actionable recommendations (including refactoring) to bring all artefacts into alignment.
review.speckit-test
Review the test automation implementation against the specification and the desired test pyramid shape; detect and explain misalignment - prioritise unit tests, identify high-value gaps and brittle tests, and provide actionable recommendations (including refactoring) to improve behavioural confidence.