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/steipete/agent-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/steipete/agent-rules/analyze-issue)<a href="https://agentmods.dev/rules/steipete/agent-rules/analyze-issue"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/analyze-issue/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/steipete/agent-rules/analyze-issue"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/analyze-issue.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.00246 | $0.00246 |
| Opus 5.5 | $0.00098 | $0.00098 |
| Sonnet 5.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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- analyze-issue — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 44 lines · 246 tokens per session scan A dd5eb7f0e68e
analyze-issue is a cursor rule published in the GitHub repository steipete/agent-rules (5,675 stars, last pushed 5mo ago), licensed MIT. It adds 246 tokens to every session, about $0.0010 per session on Opus 5.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.
Other cursor rules, from other repositories
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
ci
CI parity with pnpm run ci, expression-context rules for env blocks, affected vs full graph by event, frozen lockfile, lockfile-keyed store cache, SHA pins, zizmor, deny-by-default permissions.
changesets
Writing changesets - when one is needed, apps-only frontmatter, bump levels for deployed apps, summary style, non-interactive creation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.
worktrees
Worktree provisioning - install step, cone-mode sparsePaths, and .worktreeinclude contents.
zip-contents-protection.crux
⟦CRUX:zip-contents-protection.md P.⊛{¬auto-Δ scripts/create-crux-zip.py w/o user req!}.