Borrowing it
Nothing to install: this file belongs to vepo/issues. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vepo/issues/main/.claude/skills/review-feature-catalog/SKILL.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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.
[](https://agentmods.dev/skills/vepo/issues/review-feature-catalog)<a href="https://agentmods.dev/skills/vepo/issues/review-feature-catalog"><img src="https://agentmods.dev/badge/skills/vepo/issues/review-feature-catalog/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.
<a href="https://agentmods.dev/skills/vepo/issues/review-feature-catalog"><img src="https://agentmods.dev/badge/skills/vepo/issues/review-feature-catalog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00041 | $0.00889 |
| Opus 5 | $0.00020 | $0.00445 |
| Sonnet 5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
review-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Product Owner for Issues running a full feature-catalog review. Act as described in .claude/agents/product-owner.md. Produce a read-only product audit — do not change code or docs unless the user explicitly asks to apply fixes afterward.
Prerequisites: Read docs/feature-catalog.md, docs/domain-specification.md, and docs/backlog.md. Skim Angular routes under src/main/webui/ and relevant endpoints when verifying a row.
Scope
Default: every row in the feature catalog (UI table + API-only table) and Dev personas.
If the user names a Feature name, route prefix, or feature/<slug>.md, restrict to that subset but still note cross-feature navigation links (e.g. hub → Kanban).
Output
Write one report:
reports/feature-catalog-review-{sequential}-{dd-MM-yyyy-HH-mm-ss}.md
Severity: critical | major | minor | suggestion.
Do not ask for confirmation before starting. Do not edit src/**, catalog, or backlog in this command.
Phase 1 — Inventory
- List all catalog Feature rows (UI + API-only) with Route / API and Roles.
- Inventory Angular routes (router config) and primary shell menus.
- Note matching
feature/*.mdfiles where a capability has analysis.
Phase 2 — Route and role compliance
For each catalog row:
| Check | Pass criteria |
|---|---|
| Route exists | Path in router matches Route (params allowed) |
| Reachable | Menu or documented entry points match Steps |
| Roles | Guards / menu visibility / API roles align with Roles |
| Dev persona | At least one persona can exercise the happy path |
Mark missing implementation, extra undocumented route, or role mismatch.
Phase 3 — Happy-path steps
For each UI row, verify Steps against UI labels and flows:
- Step verbs and screen names exist (Portuguese labels as in catalog)
- Linked features (e.g. Burndown from Kanban) still exist
- Capability gates (
GET /auth/capabilities, LOCAL-only) match catalog notes - Broken or impossible steps → finding with evidence
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.
- 9d ago First seen · 109 lines · 41 tokens per session scan A d53a09400d9e
review-feature-catalog is a skill published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 889 once invoked, about $0.0002 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 skills, from other repositories
add-component
Add a new visualization component to Unovis end to end — the TypeScript core, the shared registry, the generated framework wrappers, a dev example, a gallery example, and docs. Use when asked to add/create a new component, chart type, plot, or diagram to the library, or to wire an existing core component through to…
strategy-agent
Market strategy analyst performing SWOT, competitive positioning, market-timing assessment, and go-to-market recommendations from research findings. Use after the research-agent has produced market data.
koog-assistant
Concise general-purpose assistant powered by JetBrains Koog. Use when a brief, focused answer is preferable to long-form output.
mcp-analyze-topic
Expert analyst persona used by the MCP analyze-topic tool to produce structured topic analyses. Use when invoked through the Atmosphere MCP server's analyze-topic tool.
mcp-chat-summary
Chat moderator that summarizes ongoing conversations. Use when invoked through the Atmosphere MCP server's chat-summary tool.
igniteui-blazor-generate-from-image-design
Implement Blazor application views from design images using Ignite UI Blazor components. Uses MCP servers (igniteui-cli, igniteui-theming) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working…