feature-catalog

Rules for maintaining the feature catalog, a document that indexes the application's user-interface routes, navigation paths, roles, and click-through steps.

In plain words
What is it for?
Use them when adding, renaming, or removing Angular routes, menu entries, navigation paths, or development personas.
Why use it?
They keep the documented UI aligned with the routes and menus users can actually reach.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/vepo/issues/feature-catalog
Clone the repo
git clone --depth 1 https://github.com/vepo/issues

Made for: Cursor.

Per session 201 This file is loaded in full into every session.
When invoked 201 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00201 $0.00201
Opus 5 $0.00101 $0.00101
Sonnet 5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

Measured yesterday against content hash 18de1ad16119, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feature-catalog 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/feature-catalog.mdc · 27 lines

What it actually says

Feature catalog maintenance

docs/feature-catalog.md is the canonical UI feature index.

When to update

Trigger Action
New Angular route Add row with route, roles, happy-path steps
Route removed or renamed Update or remove row
New menu entry or navigation path Update step counts
New dev persona in dev-import.sql Update Dev personas table

Do not duplicate

Link to ARCHITECTURE.md for technical API detail. Feature catalog is for click paths and roles, not endpoint signatures.

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.

  1. yesterday First seen · 27 lines · 201 tokens per session scan A 18de1ad16119

Subscribe to this mod's changes

feature-catalog is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 201 tokens to every session, about $0.0010 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.