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/py-quality/radon.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/radon)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/radon"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/radon.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.00619 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
radon 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Using Radon (Complexity & Maintainability)
Use Radon to identify high-complexity / low-maintainability hotspots and refactor them safely and incrementally.
1. Run Radon Reports
uv run radon cc -s -a . # Cyclomatic complexity (A best → F worst)
uv run radon mi -s . # Maintainability Index (100 best → 0 worst)
uv run radon hal . # (Optional) Halstead metrics
Record functions / classes with:
- Complexity grade >= C (or numeric > 10)
- Maintainability Index < 65
2. Prioritize Hotspots
Rank by (a) worst grade, (b) frequency of change (git log -S / blame), (c) business criticality.
3. Establish Safety Net
For each target file/function:
- Add / improve focused tests (behavioral, edge cases, error paths).
- Run:
uv run pytest <relevant-tests>(fast feedback) before refactor.
4. Refactor Tactics (Apply One At A Time)
- Extract Function / Method for cohesive blocks
- Decompose long conditional chains (strategy map, dict dispatch, guard clauses)
- Remove duplication (DRY) or inline trivial indirections
- Simplify boolean logic (early returns, De Morgan)
- Replace deep nesting with fail-fast exits
- Clarify names; remove commented‑out code
- Isolate side effects from pure logic
- Reduce parameter count (introduce small dataclass / typed object)
- Split large classes by responsibility (SRP)
After each micro-change:
uv run pytest <focused-scope>
uv run radon cc -s target_file.py
uv run radon mi -s target_file.py
Commit if green:
git add target_file.py tests/
git commit -m "refactor(radon): reduce complexity in <symbol> (C→B)"
5. Validate No Regression
When a file is “done”:
uv run radon cc -s -a .
uv run radon mi -s .
uv run pytest
uv run pre-commit run --all-files
6. Avoid Over-Refactoring
Stop when: (a) complexity ≤ B, (b) MI ≥ 70, (c) further change risks churn.
7. Handling Hard Cases
If complexity resists decomposition:
- Introduce a decision table / data-driven structure
- Split algorithm into phases (parse → transform → emit)
- Accept temporary adapter layer while migrating callers
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.
- 2d ago First seen · 75 lines · 0 tokens per session scan A 634e8f59140c
radon 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 619 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.