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.
git clone --depth 1 https://github.com/roy2392/vibe-agents-rulesWrote 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/rules/roy2392/vibe-agents-rules/code-analysis)<a href="https://agentmods.dev/rules/roy2392/vibe-agents-rules/code-analysis"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/code-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/roy2392/vibe-agents-rules/code-analysis"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/code-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00245 | $0.00245 |
| Opus 5.5 | $0.00098 | $0.00098 |
| Sonnet 5.5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
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 1mo 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.
This is a copy
100% identical to code-analysis — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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:
- Select analysis type based on need
- Run appropriate tools and inspections
- Generate comprehensive report
- Provide actionable recommendations
- Prioritize improvements by impact
Output Format:
- Executive summary
- Detailed findings
- Risk assessment
- Improvement roadmap
- Code examples where relevant
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.
- 1mo ago First seen · 54 lines · 245 tokens per session scan A bd3a4ada9cb1
code-analysis is a cursor rule published in the GitHub repository roy2392/vibe-agents-rules (10 stars, last pushed 1y ago), licensed MIT. It adds 245 tokens to every session, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-analysis, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
techdebt
Find and eliminate technical debt across the whole codebase — duplicated code, dead code, redundant abstractions.
code-change-refactor
This rule applies when refactoring existing code to improve quality, adopt new patterns, or integrate with newly created functionality.
validator_quality
Quality Validator — check for complexity, dead code, inconsistent naming, and technical debt.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.