code-analysis

A code inspection workflow that examines software structure, quality, performance, security, architecture, and test coverage.

In plain words
What is it for?
Use it to map component relationships, measure complexity and maintainability, find security or performance problems, and produce a prioritized improvement report.
Why use it?
It brings several types of review into one process, helping reveal risks, bottlenecks, duplication, weak boundaries, and untested paths.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/steipete/agent-rules/code-analysis
Clone the repo
git clone --depth 1 https://github.com/steipete/agent-rules
Per session 245 This file is loaded in full into every session.
When invoked 245 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00245 $0.00245
Opus 5 $0.00122 $0.00122
Sonnet 5 $0.00049 $0.00049
Haiku 4.5 $0.00024 $0.00024

Measured yesterday against content hash bd3a4ada9cb1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-analysis 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

project-rules/code-analysis.mdc · 54 lines

What it actually says

Code Analysis

Perform advanced code analysis with multiple inspection options.

Analysis Menu:

1. Knowledge Graph Generation

  • Map relationships between components
  • Visualize dependencies
  • Identify architectural patterns

2. Code Quality Evaluation

  • Complexity metrics
  • Maintainability index
  • Technical debt assessment
  • Code duplication detection

3. Performance Analysis

  • Identify bottlenecks
  • Memory usage patterns
  • Algorithm complexity
  • Database query optimization

4. Security Review

  • Vulnerability scanning
  • Input validation checks
  • Authentication/authorization review
  • Sensitive data handling

5. Architecture Review

  • Design pattern adherence
  • SOLID principles compliance
  • Coupling and cohesion analysis
  • Module boundaries

6. Test Coverage Analysis

  • Coverage percentages
  • Untested code paths
  • Test quality assessment
  • Missing edge cases

Process:

  1. Select analysis type based on need
  2. Run appropriate tools and inspections
  3. Generate comprehensive report
  4. Provide actionable recommendations
  5. Prioritize improvements by impact

Output Format:

  • Executive summary
  • Detailed findings
  • Risk assessment
  • Improvement roadmap
  • Code examples where relevant
Changes

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.

  1. yesterday First seen · 54 lines · 245 tokens per session scan A bd3a4ada9cb1

Subscribe to this mod's changes

code-analysis is a cursor rule published in the GitHub repository steipete/agent-rules (5,696 stars, last pushed 4mo ago), licensed MIT. It adds 245 tokens to every session, about $0.0012 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-30.