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 Swallow100/gpt-5.6-stop-overengineering --skill gpt56-stop-overengineeringgit clone --depth 1 https://github.com/Swallow100/gpt-5.6-stop-overengineeringWrote 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/swallow100/gpt-5.6-stop-overengineering/gpt56-stop-overengineering)<a href="https://agentmods.dev/skills/swallow100/gpt-5.6-stop-overengineering/gpt56-stop-overengineering"><img src="https://agentmods.dev/badge/skills/swallow100/gpt-5.6-stop-overengineering/gpt56-stop-overengineering/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/swallow100/gpt-5.6-stop-overengineering/gpt56-stop-overengineering"><img src="https://agentmods.dev/badge/skills/swallow100/gpt-5.6-stop-overengineering/gpt56-stop-overengineering.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.00084 | $0.00836 |
| Opus 5.5 | $0.00034 | $0.00334 |
| Sonnet 5.5 | $0.00017 | $0.00167 |
| Haiku 4.5 | $0.00008 | $0.00084 |
Grade A, and why
gpt56-stop-overengineering 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GPT-5.6 Stop Overengineering
Make the smallest safe change. Produce proportionate proof. Then stop.
1. Lock the contract
Before editing, reduce the task to four lines:
- Outcome: the observable result the user requested.
- Scope: the files, behavior, or subsystem that owns that result.
- Constraints: explicit limits plus repository instructions.
- Proof: the least expensive evidence that can establish success.
Infer these from available context when they are clear. Ask only when a missing answer would materially change the implementation or create meaningful risk.
Do not silently add goals. Treat appealing improvements as optional follow-ups, not requirements.
2. Choose the smallest sufficient change
Prefer, in order:
- Reuse an existing path, pattern, or dependency.
- Modify the narrowest ownership boundary.
- Add the least new code needed for the requested behavior.
Do not add an abstraction for one hypothetical future use. Do not introduce a dependency, framework, configuration surface, public API, migration, compatibility layer, or broad refactor unless the contract requires it.
Preserve unrelated code, formatting, comments, and user changes. Avoid cleanup whose only justification is "while here."
Before expanding into another subsystem or materially growing the expected diff, pause and either choose a narrower solution or request approval.
3. Verify in proportion to risk
Select the lowest tier that can realistically catch a regression introduced by the change:
| Risk | Typical change | Required proof |
|---|---|---|
| Low | prose, comments, static copy, local style | inspect the diff; render or lint only when relevant |
| Medium | isolated logic, component behavior, bug fix | reproduce or run focused tests for the changed behavior |
| High | security, permissions, data, migrations, public contracts, shared infrastructure, release paths | focused tests plus the relevant broader checks and failure paths |
Follow mandatory repository or user-specified checks even when they exceed this table.
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.
- 2mo ago First seen · 78 lines · 84 tokens per session scan A 6d6ba36f3ed0
gpt56-stop-overengineering is a skill published in the GitHub repository Swallow100/gpt-5.6-stop-overengineering (4 stars, last pushed 2mo ago), licensed MIT. It adds 84 tokens to every session and 836 once invoked, about $0.0003 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-31.
Other skills, from other repositories
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…
128-java-generics
Use when you need to review, improve, or refactor Java code for generics quality — including avoiding raw types, applying the PECS (Producer Extends Consumer Super) principle for wildcards, using bounded type parameters, designing effective generic methods, leveraging the diamond operator, understanding type erasure…
322-frameworks-spring-boot-testing-integration-tests
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code…
422-frameworks-quarkus-testing-integration-tests
Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST…
521-frameworks-micronaut-testing-unit-tests
Use when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and Test vs IT naming. For framework-agnostic Java use @131-java-testing-unit-testing.…