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 mohitmishra786/anti-vibe-skills --skill complexity-copgit clone --depth 1 https://github.com/mohitmishra786/anti-vibe-skillsWrote 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/mohitmishra786/anti-vibe-skills/complexity-cop)<a href="https://agentmods.dev/skills/mohitmishra786/anti-vibe-skills/complexity-cop"><img src="https://agentmods.dev/badge/skills/mohitmishra786/anti-vibe-skills/complexity-cop/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/mohitmishra786/anti-vibe-skills/complexity-cop"><img src="https://agentmods.dev/badge/skills/mohitmishra786/anti-vibe-skills/complexity-cop.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.00075 | $0.01288 |
| Opus 5 | $0.00037 | $0.00644 |
| Sonnet 5 | $0.00015 | $0.00258 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
complexity-cop 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
complexity-cop
Purpose
Flag over-engineering by name and describe its impact — never suggest how to simplify, never propose an alternative, never make the simplification judgment call that belongs to the human.
Hard Refusals
- Never suggest a simpler alternative — "you could just use X instead" removes the human's simplification judgment.
- Never estimate effort to simplify — "this would be easy to simplify" is a nudge toward a specific decision.
- Never say "this is too complex" as a verdict. Name the specific complexity pattern and its specific cost. Verdicts are for the human.
- Never approve a level of complexity — "this seems reasonable" is not the AI's call.
- Never conflate complexity with incorrectness — complexity may be warranted. The AI's job is to make the cost visible, not to conclude it is unjustified.
Triggers
- A proposed solution with more than three moving parts for a problem that sounds straightforward
- Introduction of abstraction layers before the concrete case is proven
- Generalization of a solution before a second use case exists
- "We'll need this to be extensible / flexible / configurable for the future"
- "The standard enterprise pattern for this is..."
- Any solution that requires a diagram to explain a problem that fits in a sentence
Workflow
1. Name the complexity pattern
Read the proposed solution and identify which complexity patterns are present. Name each one.
| Pattern | Description |
|---|---|
| Premature abstraction | Abstract interface before two concrete implementations exist |
| Speculative generality | Built for use cases that don't exist yet |
| Unnecessary indirection | Data or control passes through layers with no transformation |
| Configuration over convention | Behavior controlled by config that is always the same value |
| Framework over function | Framework chosen when a function would suffice |
| Distributed over simple | Network boundary introduced where a function call would work |
| Async over sync | Asynchrony introduced without a concrete concurrency requirement |
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 · 119 lines · 75 tokens per session scan A b7305b7cc2ec
complexity-cop is a skill published in the GitHub repository mohitmishra786/anti-vibe-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 75 tokens to every session and 1,288 once invoked, about $0.0004 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-31.
Other skills, from other repositories
refactoring-workflow
Improve the structure of existing code without changing its behaviour, in small verified steps under a green test suite. Use when the user asks to refactor, clean up, restructure or simplify code, wants to reduce duplication or coupling, is preparing a codebase for a feature it cannot currently accommodate, or when…
code-quality-review
A code-review guide for judging whether software stays easy to understand, change, test, and extend.
codebase-organizer
Universal codebase operations: analyze, organize, and architecturally deepen any repo. Two commands: /organize for read-only analysis and /deepen for multi-agent refactoring. Use when the user wants a codebase scan, deep module scoring, dependency mapping, architectural improvement, or code-to-skill conversion.…
arch-optimize
A software architecture review workflow that scans a codebase for structural risks and measures code quality. It checks issues such as overly complex code, repeated knowledge, changes spreading across many files, circular dependencies, and distorted domain models.
improve-codebase-architecture
Use when surfacing architectural friction inside a single EVOKORE bounded context and proposing deepening refactors (shallow modules, leaky seams, low locality) that turn shallow modules into deep ones — informed by ADR-0005 bounded contexts and the project's domain language.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.