ave: Skill for Claude Code

.claude/skills/to-prd/SKILL.md

to-prd is a skill for Claude Code from aveproject/ave. It costs 0 tokens per session (105 once invoked), scanned A, original, Apache-2.0.

A planning format for larger coordinated changes. A PRD, or product requirements document, records the work when it affects the schema, a detection engine, or a batch of related records.

In plain words
What is it for?
Planning schema changes, new rule-engine categories, or groups of related AVE records in docs/agents/prds/.
Why use it?
It prevents broad changes from being handled like a one-file edit and makes clear when the scanner must be coordinated.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is aveproject/ave's own configuration. It tells Claude Code how to work on ave itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ave configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aveproject/ave. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/aveproject/ave/main/.claude/skills/to-prd/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aveproject/ave

Made for: Claude Code.

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.

agentmods badge for to-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/aveproject/ave/to-prd/github.svg)](https://agentmods.dev/skills/aveproject/ave/to-prd)
Your own site
<a href="https://agentmods.dev/skills/aveproject/ave/to-prd"><img src="https://agentmods.dev/badge/skills/aveproject/ave/to-prd/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.

agentmods 80×15 button for to-prd

Your own site · 80×15
<a href="https://agentmods.dev/skills/aveproject/ave/to-prd"><img src="https://agentmods.dev/badge/skills/aveproject/ave/to-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 105 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00105
Opus 5.5 $0.00000 $0.00042
Sonnet 5.5 $0.00000 $0.00021
Haiku 4.5 $0.00000 $0.00011

Measured 1mo ago against content hash 7e268657024c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

to-prd 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 1mo 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-prd/SKILL.md · 13 lines

What it actually says

to-prd — ave

For larger work (schema changes, new rule engine, bulk record additions). A single record uses add-ave-record, not a PRD.

Save to docs/agents/prds/. Use when:

  • Changing the record schema (affects all records + the scanner)
  • Adding a new detection engine category
  • A coordinated batch of related AVE records (e.g. a new attack family)

Add field: "Scanner coordination required: yes/no" Schema changes always require scanner coordination.

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. 1mo ago First seen · 13 lines · 0 tokens per session scan A 7e268657024c

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

skill-inspector

Review AI agent skills before installation using NVIDIA SkillSpector and source-aware semantic review. Use when asked whether a skill or downloaded skill folder is safe, trustworthy, installable, over-permissioned, or malicious.

NVIDIA/SkillSpector · 47 tokens

stock-report

Prepare a read-only availability report from an identified stock snapshot. Use when a task asks whether a stated quantity is available, without reserving or ordering stock.

RenatoMignone/From-LLMs-to-Secure-Agents · 34 tokens

crossval-harness

Orchestrate a static + dynamic, exploit-validated red-team of an AI agent — read the source to find candidate vulnerable paths, then run the dynamic skills to confirm or refute each one empirically. The arbiter of truth is whether the exploit works, not a model vote. Authorized testing of agents you own or are…

William2333ZZ/trustshell · 75 tokens

redteam-an-agent

The end-to-end methodology for red-teaming a specific AI agent — adaptively, exploit-validated, and honestly. Read THIS target's own code, stand up a disposable harness, and prove or refute each weakness through a real attacker-reachable entry point. This is the orchestration + discipline that makes a finding…

William2333ZZ/trustshell · 90 tokens

audit-agent-code

Security-audit an AI agent's OWN framework code for classic appsec vulnerabilities the LLM can't defend — path traversal, command injection, SSRF, fail-open security controls, missing/late auth, unsafe deserialization — especially at the untrusted-input boundaries (channels, file/media handlers, config & skill…

William2333ZZ/trustshell · 102 tokens

rt6-memory-poisoning

Red-team an AI agent's persistent memory for cross-session prompt injection ("memory poisoning") — does untrusted content the agent processes get written into long-term memory and re-fire in future sessions with no attacker present? Authorized testing of agents you own or are permitted to test.

William2333ZZ/trustshell · 61 tokens