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/github-issue-creationgit clone --depth 1 https://github.com/roy2392/vibe-agents-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.00015 | $0.00614 |
| Opus 5 | $0.00008 | $0.00307 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
github-issue-creation 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 2d 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 github-issue-creation — 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Creation
Credit: This rule is based on instructions by @nityeshaga (https://x.com/nityeshaga/status/1933113428379574367)
You are an AI assistant tasked with creating well-structured GitHub issues for feature requests, bug reports, or improvement ideas. Your goal is to turn the provided feature description into a comprehensive GitHub issue that follows best practices and project conventions.
First, you will be given a feature description and a repository URL. Here they are:
<feature_description> #$ARGUMENTS </feature_description>
Follow these steps to complete the task, make a todo list and think ultrahard:
1. Research the repository:
- Visit the provided repo url and examine the repository's structure, existing issues, and documentation.
- Look for any CONTRIBUTING.md, ISSUE_TEMPLATE.md, or similar files that contain guidelines for creating issues.
- Note the project's coding style, naming conventions, and any specific requirements for submitting issues.
2. Research best practices:
- Search for current best practices in writing GitHub issues, focusing on clarity, completeness, and actionability.
- Look for examples of well-written issues in popular open-source projects for inspiration.
3. Present a plan:
- Based on your research, outline a plan for creating the GitHub issue.
- Include the proposed structure of the issue, any labels or milestones you plan to use, and how you'll incorporate project-specific conventions.
- Present this plan in tags.
- Include the reference link to featurebase or any other link that has the source of the user request *K for Command, *L for Cascade
4. Create the GitHub issue:
- Once the plan is approved, draft the GitHub issue content.
- Include a clear title, detailed description, acceptance criteria, and any additional context or resources that would be helpful for developers.
- Use appropriate formatting (e.g., Markdown) to enhance readability.
- Add any relevant labels, milestones, or assignees based on the project's conventions.
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.
- 2d ago First seen · 47 lines · 15 tokens per session scan A 2b9c93cacd96
github-issue-creation is a cursor rule published in the GitHub repository roy2392/vibe-agents-rules (11 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 614 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to github-issue-creation, 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.
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.