Borrowing it
Nothing to install: this file belongs to Insight-Services-APAC/ingenious. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Insight-Services-APAC/ingenious/main/.claude/commands/quality/js-quality/complexity.mdgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/insight-services-apac/ingenious/complexity)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/complexity"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/complexity.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.00000 | $0.00475 |
| Opus 5 | $0.00000 | $0.00237 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
complexity 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 yesterday.
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
Refactor Using Complexity Analysis (ESLint Complexity Rules)
Use ESLint complexity rules to identify high-complexity functions and refactor them safely.
1. Run Complexity Analysis
# Check cyclomatic complexity with ESLint
npx eslint . --ext .js,.ts,.vue --rule 'complexity: ["warn", 10]'
2. Identify Hotspots
Target functions with:
- Cyclomatic complexity > 10
- Many branches (if/else, switch)
- Deep nesting levels
- High cognitive complexity
3. Configure ESLint Rules
Add to .eslintrc.js:
{
rules: {
'complexity': ['warn', { max: 10 }],
'max-depth': ['warn', 4],
'max-nested-callbacks': ['warn', 3],
'max-lines-per-function': ['warn', { max: 50 }]
}
}
4. Refactor Tactics (Apply One At A Time)
- Extract function for cohesive logic blocks
- Replace conditionals with early returns (guard clauses)
- Use object lookup maps instead of switch statements
- Replace nested callbacks with async/await
- Decompose large functions by responsibility
- Extract complex conditions into named functions
- Use strategy pattern for variant behavior
- Split components with multiple concerns
After each change:
npm test
npx eslint <target_file> --rule 'complexity: ["error", 10]'
Commit if passing:
git add <files>
git commit -m "refactor(complexity): reduce complexity in <function>"
5. Validate No Regression
When a file is improved:
npx eslint . --ext .js,.ts,.vue
npm test
npm run build:check
6. Avoid Over-Refactoring
Stop when:
- Complexity <= 10
- Max nesting <= 3
- Function length reasonable
- Further splitting reduces readability
7. Final Quality Gate
npx eslint . --ext .js,.ts,.vue
npm run build:check
npm test
Goal: No functions with cyclomatic complexity above 10.
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.
- yesterday First seen · 83 lines · 0 tokens per session scan A fa31816c9a4a
complexity is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 475 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-09-04.
Other commands, from other repositories
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
flutter-build
Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
analyze-deps
Analyze the project's dependency tree, identify unused or duplicate dependencies, and suggest optimizations.
fix-issue
Command "fix-issue" from HKTITAN/cursor-best-practices, covering steps and rules.
speckit.review.errors
Error handling review — silent failure detection, catch block analysis, error logging.