A project rule for managing GitHub issues, which are tracked work items for bugs, tasks, or requests. It requires issue text in English and asks developers to update checklists, acceptance criteria, comments, and status after implementation.

Use it when creating or implementing GitHub issues. It helps record scope, verify completion, summarize shipped work, and leave unfinished items visible.

It keeps the written plan aligned with what was actually delivered. It also prevents issues from being closed when required work remains.

issues — Cursor rule for Cursor by multei/web

Install

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.

Clone the repo

git clone --depth 1 https://github.com/multei/web

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/multei/web/issues/github.svg)](https://agentmods.dev/rules/multei/web/issues)

Your own site

<a href="https://agentmods.dev/rules/multei/web/issues"><img src="https://agentmods.dev/badge/rules/multei/web/issues/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/multei/web/issues"><img src="https://agentmods.dev/badge/rules/multei/web/issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 193 This file is loaded in full into every session.

When invoked 193 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00193	$0.00193
Opus 5.5	$0.00077	$0.00077
Sonnet 5.5	$0.00039	$0.00039
Haiku 4.5	$0.00019	$0.00019

Measured yesterday against content hash 6db0688c2cfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issues 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.

.cursor/rules/issues.mdc · 22 lines

What it actually says

GitHub issues

Write all issues in English (title and body). Do not create Portuguese issues.
Prefer Conventional Commit-style titles when helpful (ci: …, docs: …, feat: …).

When you implement a GitHub issue:

Read the full issue body (scope, acceptance criteria, notes) before and during the work.
After implementation finishes, edit the issue:
- Check completed checklist items (- [x]).
- Leave incomplete items unchecked and note what remains.
- Update acceptance criteria the same way.
Comment with a short English summary of what shipped and any follow-ups.
Close only when acceptance criteria are met; otherwise leave open/reopen with pending items visible.

See CONTRIBUTING.md and AGENTS.md.

Changes

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 · 22 lines · 193 tokens per session scan A 6db0688c2cfd

Subscribe to this mod's changes

issues is a cursor rule published in the GitHub repository multei/web (4 stars, last pushed today), licensed MIT. It adds 193 tokens to every session, about $0.0008 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-11-07.

Project management gatsby gatsby-site netlify

issues next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
issuesmultei/web	Cursor rule	4	today	MIT	A	193	Cursor
backendnixopus/nixopus	Cursor rule	1.5k	7d ago	none	A	0	Cursor
installer_clinixopus/nixopus	Cursor rule	1.5k	7d ago	none	A	0	Cursor
frontendnixopus/nixopus	Cursor rule	1.5k	7d ago	none	A	0	Cursor
ponytailDietrichGebert/ponytail	Cursor rule	186k	9d ago	MIT	A	604	Cursor
angular-20angular/angular	Cursor rule	101k	yesterday	MIT	A	0	Cursor
dev-standardapache/superset	Cursor rule	75k	yesterday	Apache-2.0	A	1,147	Cursor