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/emissium/cursor-rules/github_issues_prsgit clone --depth 1 https://github.com/emissium/cursor-rulesWhat 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.02070 | $0.02070 |
| Opus 5 | $0.01035 | $0.01035 |
| Sonnet 5 | $0.00414 | $0.00414 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade A, and why
github_issues_prs 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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues & PR Creation (Canonical, Idempotent, Newline-Safe)
Purpose
Standardize creation of GitHub issues and pull requests so they are:
- newline-safe (no
\nartifacts; bodies preserved via file-F) - deduplicated before creation
- labeled consistently and thoughtfully
- auto-assigned to the requestor
- linked to Knowledge Graph (
Task:* → GitHub: <url>) with a single canonical link
This rule builds on the repo workflow policy and must be followed for all task/feature/bug work.
Prerequisites
- Authenticated GitHub CLI:
gh auth status
- Dynamic repo slug (never hardcode):
SLUG=$(gh repo view --json nameWithOwner -q .nameWithOwner)
- If unset default repo causes errors:
gh repo set-default "$SLUG"
Title & Label Conventions
- Issue titles follow:
P{0|1|2}: <TaskName> — <short description> - Labels policy:
- Default type:
enhancementfor tasks/features; usebugfor defects - Priority: add exactly one of
priority:P0|priority:P1|priority:P2based on title prefix - Area: add one or more of:
area:api,area:worker,area:infra,area:docs,area:client - Kind: optionally add
kind:refactor,kind:perf,kind:security,kind:ci - Status: optionally add
status:ready|status:blocked
- Default type:
Recommended minimal label sets:
- Features:
enhancement,priority:P?,area:<x> - Bugs:
bug,priority:P?,area:<x>
Assignment
- Always assign the creator:
--assignee "@me" - Optional reviewers for PRs:
--reviewer "@me"(self-review placeholder) and add teammates as needed.
Newline-Safe Bodies (Fix for \n token bleed)
ALWAYS write the body to a file and pass with -F/--body-file. Use single-quoted heredocs to preserve literal newlines and avoid shell interpolation.
Example:
cat > /tmp/issue.md <<'EOF'
Context: why this is needed
Acceptance criteria:
- item 1
- item 2
EOF
gh issue create --repo "$SLUG" -t "P1: My Task — short" -F /tmp/issue.md \
--label enhancement --label "priority:P1" --label "area:api" \
--assignee "@me"
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.
- yesterday First seen · 232 lines · 2,070 tokens per session scan A c9dcfc5547c0
github_issues_prs is a cursor rule published in the GitHub repository emissium/cursor-rules (7 stars, last pushed 9mo ago), licensed MIT. It adds 2,070 tokens to every session, about $0.0103 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-31.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.