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 skills/yuri-semenenko/ai-engineering-workspace/complexity-auditnpx skills add yuri-semenenko/ai-engineering-workspace --skill complexity-auditgit clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspaceWrote 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/yuri-semenenko/ai-engineering-workspace/complexity-audit)<a href="https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/complexity-audit"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/complexity-audit.svg" alt="Measured on agentmods" 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.00117 | $0.00565 |
| Opus 5 | $0.00059 | $0.00282 |
| Sonnet 5 | $0.00023 | $0.00113 |
| Haiku 4.5 | $0.00012 | $0.00056 |
Grade A, and why
complexity-audit 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 6d 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
Complexity Audit
Find accidental complexity that already shipped. This is a standing-codebase scan, not a diff review — use /code-review or /simplify for the current change.
How to run (keep main context lean)
- Map the tree first. If a path argument was given, scope the whole audit to that subtree; otherwise take the whole repo. Identify top-level subsystems / packages from the layout (workspaces,
src/domains, services). - Fan out, do not grep inline. Per the persona's session-hygiene rule, dispatch
Exploresubagents — one per subsystem — each tasked to surface over-engineering only. Each returns a compact findings list, not file dumps. This keeps large intermediate output out of the main conversation. - Dedup and prioritize the merged findings before reporting.
What counts as over-engineering (the persona's anti-patterns)
- Premature abstraction / speculative generality (interfaces with one implementation, config for things that never vary).
- Pattern-heavy designs where a function would do (factories, managers, base classes added "for the future").
- Needless layering / indirection with no payoff; wrapper modules that only re-export.
- Framework-driven architecture: structure dictated by a framework, not the domain.
- Dead code, unused flags, config that no longer changes behavior.
- Tight coupling and leaky abstractions hidden behind "clean" names.
Do not flag: intentional // TRADEOFF(...) annotations (those are tracked by /debt-ledger), validation, error handling, security, or tested invariants.
Output
Prioritized report, most-impactful first. For each finding:
| Severity | Location (file:line) |
What's over-built | Why it doesn't pay for itself | Proposed simplification | Risk of removing |
|---|
Severity = blast radius × how speculative it is. End with a short "highest-leverage deletions" shortlist. State assumptions explicitly. No marketing prose.
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.
- 6d ago First seen · 36 lines · 117 tokens per session scan A d0e76e454898
complexity-audit is a skill published in the GitHub repository yuri-semenenko/ai-engineering-workspace (1 stars, last pushed 5d ago), licensed MIT. It adds 117 tokens to every session and 565 once invoked, about $0.0006 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
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…
codex-review
Use this skill when users ask for code review, review pending changes, or inspect the latest commit with Codex-based review workflows. It prepares context, runs project linting, and reviews the result.
phoenix-review
Review completed work against the Intent Contract's acceptance criteria using objective evidence, not opinion — re-run every check, confirm no regressions, inspect the tamper-evident trace, and surface only real issues (bugs, unmet criteria, regressions). Use before shipping, after a feature is built, or when the user…
analyze
Deep-analyzes the current codebase to discover stack, architecture, patterns, conventions, and pitfalls. Creates curated documentation in .vibeflow/ that persists and can be committed to git. Supports incremental updates, scoped deep-dives, interactive review, and satellite repo analysis. Use when setting up a…
ndv-temporal
Trajectory-aware cognitive module. Injects lifecycle and direction-of-change thinking into architecture reviews, dependency audits, and technology selection — where direction matters as much as current state. Emergent.