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 skills add stefanrossmeier/ai-craftkit --skill overengineering-reviewgit clone --depth 1 https://github.com/stefanrossmeier/ai-craftkitWrote 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/skills/stefanrossmeier/ai-craftkit/overengineering-review)<a href="https://agentmods.dev/skills/stefanrossmeier/ai-craftkit/overengineering-review"><img src="https://agentmods.dev/badge/skills/stefanrossmeier/ai-craftkit/overengineering-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/skills/stefanrossmeier/ai-craftkit/overengineering-review"><img src="https://agentmods.dev/badge/skills/stefanrossmeier/ai-craftkit/overengineering-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.00000 | $0.06586 |
| Opus 5 | $0.00000 | $0.03293 |
| Sonnet 5 | $0.00000 | $0.01317 |
| Haiku 4.5 | $0.00000 | $0.00659 |
Grade A, and why
overengineering-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 11d 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 — 1,040 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overengineering Review Skill
Command: /overengineering-review
Generate an evidence-based review of accidental and unjustified implementation complexity in the currently opened repository.
The skill inspects the complete repository, reconstructs the problem the software actually has to solve, identifies implementation complexity that appears disproportionate to that problem, challenges each candidate against legitimate constraints, and writes a pragmatic report to the repository's docs/ folder.
Invocation Model
Use this skill when the user calls:
/overengineering-review
This is a skill invocation, not a shell command. It has no command-line parameters, flags, modes, or options.
If the user adds text around or after the invocation, treat that text as plain-language review guidance. Do not parse it as command syntax.
Examples of guidance:
- focus on one subsystem or product area
- pay special attention to abstractions, configuration, infrastructure, or extensibility
- review whether the architecture is justified by the current scale
- distinguish deliberate security boundaries from unnecessary indirection
- challenge complexity introduced for hypothetical future requirements
Do not document or advertise flag-based usage for this skill.
Purpose
/overengineering-review identifies places where the cost of a solution appears greater than the problem, requirement, risk, or demonstrated scale justifies.
The primary question is:
What complexity exists because the problem requires it, and what complexity exists because the chosen solution introduced it?
Use Fred Brooks' distinction as the conceptual baseline:
- Essential complexity: complexity inherent in the problem, domain, constraints, or required qualities.
- Accidental complexity: complexity introduced by implementation choices, architecture, tools, abstractions, processes, or infrastructure.
Accidental complexity is not automatically overengineering. A finding requires evidence that the additional complexity is not sufficiently justified by current or clearly evidenced requirements, constraints, risks, or near-term needs.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 1,040 lines · 0 tokens per session scan A a02579e9239c
overengineering-review is a skill published in the GitHub repository stefanrossmeier/ai-craftkit (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,586 tokens. 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-31.
Other skills, from other repositories
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
clean-code
Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead.
concurrency-review
Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
java-code-review
Systematic code review for Java with null safety, exception handling, concurrency, and performance checks. Use when user says "review code", "check this PR", "code review", or before merging changes.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.