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.
npx agentmods add rules/roy2392/vibe-agents-rules/analyze-issuegit 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/analyze-issue)<a href="https://agentmods.dev/rules/roy2392/vibe-agents-rules/analyze-issue"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/analyze-issue.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 | $0.00246 | $0.00246 |
| Opus 5 | $0.00123 | $0.00123 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
analyze-issue 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 3d 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 analyze-issue — 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
Analyze Issue
Fetch GitHub issue details and create a comprehensive implementation specification.
Template Sections:
1. Issue Summary
Brief overview of the issue
2. Problem Statement
Clear definition of what needs to be solved
3. Technical Approach
High-level solution approach and architecture decisions
4. Implementation Plan
Step-by-step breakdown of implementation tasks
5. Test Plan
Testing strategy and test cases to write
6. Files to Modify
List of existing files that need changes
7. Files to Create
New files that need to be created
8. Existing Utilities to Leverage
Project utilities/helpers that can be reused
9. Success Criteria
Measurable criteria for completion
10. Out of Scope
What won't be addressed in this implementation
Process:
- Fetch issue details using
gh issue view <issue_number> - Review related code and project structure
- Analyze requirements thoroughly
- Create detailed technical specification
- Follow strict TDD principles, KISS approach
- Enforce 300-line file limit where applicable
- Output the full technical specification for review
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.
- 3d ago First seen · 44 lines · 246 tokens per session scan A dd5eb7f0e68e
analyze-issue is a cursor rule published in the GitHub repository roy2392/vibe-agents-rules (11 stars, last pushed 1y ago), licensed MIT. It adds 246 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analyze-issue, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.