Borrowing it
Nothing to install: this file belongs to okfriansyah-moh/ares. 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/okfriansyah-moh/ares/main/.ai/skills/spaghetti-code-review/SKILL.mdgit clone --depth 1 https://github.com/okfriansyah-moh/aresWrote 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/okfriansyah-moh/ares/spaghetti-code-review)<a href="https://agentmods.dev/skills/okfriansyah-moh/ares/spaghetti-code-review"><img src="https://agentmods.dev/badge/skills/okfriansyah-moh/ares/spaghetti-code-review.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.00864 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
spaghetti-code-review 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spaghetti Code Review
Purpose
Review a codebase for tangled, hard-to-change code and classify functions, files, and folders by maintainability risk with concrete recommendations and solutions.
Inputs
- Repository structure, source files, tests, generated artifacts, and build configuration.
- Existing architecture, contribution, style, and testing guidance.
- Recent diffs or target scope when the review is limited to a feature, PR, package, or module.
- Available static analysis, test coverage, dependency graph, complexity, duplication, and lint output.
Classification
Healthy: clear responsibility, low coupling, readable flow, focused tests, and stable boundaries.Watchlist: mostly understandable, but showing early signs of growth, duplication, long functions, weak names, or scattered knowledge.Tangled: multiple responsibilities, hidden side effects, unclear dependencies, brittle conditionals, or tests that make change difficult.Spaghetti: control flow, state, dependencies, naming, and boundaries are so mixed that local changes are risky without refactoring.Critical Hotspot: high-change or high-impact spaghetti code that also affects security, data integrity, user-visible behavior, releases, or core architecture.
Review Method
- Start with a repository map: identify languages, entry points, major folders, generated code, test boundaries, and ownership conventions.
- Review from broad to narrow: classify folders first, then files, then the functions or methods that explain the risk.
- Use evidence, not taste: cite concrete signals such as branching depth, function length, global state, cyclic dependencies, duplicate logic, mixed abstraction levels, temporal coupling, poor error handling, missing tests, or architecture drift.
- Separate symptoms from causes: describe what is tangled, why it became risky, and what change pressure will make it worse.
- Distinguish code smells from intentional design: do not penalize adapters, generated files, simple scripts, or framework glue without evidence of change risk.
- Prefer incremental repair plans over rewrites unless the code is isolated, low-risk, and cheaper to replace than untangle.
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.
- 7d ago First seen · 63 lines · 0 tokens per session scan A eeaa5459efd7
spaghetti-code-review is a skill published in the GitHub repository okfriansyah-moh/ares (2 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 864 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-08-31.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
codegraph
A local code-graph query tool for an existing project. It maps symbols and their relationships so you can search for definitions, callers, callees, affected files, and focused context.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.