to-issues

A guide for turning a product requirements document into a set of development issues. In the AVE project, an issue usually covers one security record, its detection rule, and two test examples.

In plain words
What is it for?
Use it when planning AVE work from a requirements document. It also explains how to divide schema changes into separate updates for validation, existing records, and scanner integration.
Why use it?
It breaks broad plans into concrete pieces of work that can be implemented and tracked separately.

Skill for Claude CodeCodex

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 skills/aveproject/ave/to-issues
Any agent
npx skills add aveproject/ave --skill to-issues
Clone the repo
git clone --depth 1 https://github.com/aveproject/ave

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 81 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00081
Opus 5 $0.00000 $0.00041
Sonnet 5 $0.00000 $0.00016
Haiku 4.5 $0.00000 $0.00008

Measured 2d ago against content hash bfd32778dc9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/skills/to-issues/SKILL.md · 11 lines

What it actually says

to-issues — ave

Break a PRD into issues. For AVE work, each issue is usually one record (record + rule + 2 fixtures) — already vertical by nature.

Schema changes are the exception: slice into

  1. schema field addition
  2. validation script update
  3. backfill existing records
  4. scanner-side consumption (coordinate with bawbel/scanner)
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. 2d ago First seen · 11 lines · 0 tokens per session scan A bfd32778dc9c

Subscribe to this mod's changes

to-issues is a skill published in the GitHub repository aveproject/ave (17 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 81 tokens. 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-30.