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/vepo/issues/backlog-managementgit clone --depth 1 https://github.com/vepo/issuesWhat 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.00423 | $0.00423 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
backlog-management 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.
What it actually says
Backlog management
Canonical backlog: docs/backlog.md.
Always
- Treat the backlog as an ordered table — column Order (integer, lower = higher priority).
- When adding, removing, promoting, completing, or deprioritizing ideas, update the table and renumber Order so active (
idea/ready) ranks stay contiguous starting at 1. - Prefer reordering over long prose lists; keep one row per idea.
When to update
| Trigger | Action |
|---|---|
| User asks for ideas / backlog / prioritization | Propose rows; write them into docs/backlog.md if accepted |
| New product idea in chat (not starting analysis yet) | Add idea row; assign Order |
| Starting feature analysis for a backlog idea | Status → promoted; link feature/<slug>.md |
Feature changelog marked done |
Matching backlog row → done (or remove from active ranks and renumber) |
| User rejects an idea | Status → wont; renumber remaining |
| User says “prioritize X” / “move Y up” | Reorder Order values; do not invent silent priority changes |
Do not
- Put implementation tasks (T1, T2…) in the backlog — those live in
feature/*.md. - Duplicate the full feature analysis in the backlog — one-line Why / notes + slug + link.
- Start phase 5 coding from a backlog row alone — still follow development-process.mdc.
Relation to feature docs
backlog idea → feature analysis (feature/<slug>.md) → … → done
↑ ↓
Order / Status Status: promoted + Feature doc link
Promoted work may keep a backlog row for visibility until done.
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 · 42 lines · 423 tokens per session scan A 18371f82d297
backlog-management is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 423 tokens to every session, about $0.0021 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
project-context
EDDI Backend — AI Agent Instructions. Complete project context, architecture, and coding guidelines.
cli-forge-schema
Generate GitHub-compatible Mermaid diagrams — auto-picks diagram type, splits complex ones, converts tables/kanban/PERT.
project-modules-and-stack
YiSmartCloud repo stack and Maven module map.
sprint-planning
BMAD BMM Agent: sprint-planning.
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.