automatos-ai: Skill for Claude Code

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

prd-classify is a skill for Claude Code from AutomatosAI/automatos-ai. It costs 47 tokens per session (907 once invoked), scanned A, original, Apache-2.0.

A workflow for sorting an Automatos product-requirements document into one of four work types: reuse, refactoring, extension, or a new build.

In plain words
What is it for?
It is for classifying Automatos PRDs before planning and estimating implementation.
Why use it?
It helps determine how much existing code should be reused before estimating the work.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions CLAUDE.md.

This is AutomatosAI/automatos-ai's own configuration. It tells Claude Code how to work on automatos-ai 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 automatos-ai configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AutomatosAI/automatos-ai. 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/AutomatosAI/automatos-ai/main/.claude/skills/prd-classify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/AutomatosAI/automatos-ai

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 prd-classify

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/automatosai/automatos-ai/prd-classify"><img src="https://agentmods.dev/badge/skills/automatosai/automatos-ai/prd-classify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 907 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.00047 $0.00907
Opus 5.5 $0.00019 $0.00363
Sonnet 5.5 $0.00009 $0.00181
Haiku 4.5 $0.00005 $0.00091

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

Security

Grade A, and why

prd-classify 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/prd-classify/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PRD Classifier

Slash command: /prd-classify <PRD#> or /prd-classify (then paste the PRD).

This skill enforces CLAUDE.md §3 ("REUSE over BUILD"). It surfaces existing surfaces in the codebase before estimating, so a PRD doesn't get costed as net-new when it's actually a relabel.

Workflow

1. Read the PRD

Locate the PRD file in docs/PRDs/ or wherever the user dropped it. Read it end-to-end. Note:

  • The stated goal
  • The user-facing artifacts mentioned (pages, components, tables, tools, agents)
  • Any "build / create / add" language

2. Map existing surfaces (mandatory)

For each artifact mentioned in the PRD, check what already exists. Use parallel searches:

  • Frontend components: grep -rli "<artifact>" frontend/components/
  • Hooks: find frontend/hooks -type f | xargs grep -li "<artifact>"
  • API routers: grep -rl "@router\." orchestrator/api/ | xargs grep -l "<artifact>"
  • DB tables: grep -rE "class \w+\(.*Base" orchestrator/modules/ orchestrator/core/ | grep -i "<artifact>"
  • Platform tools: read orchestrator/core/platform/platform_actions.py
  • Skills: ls ../automatos-skills/
  • Knowledge graph: query graphify-out/graph.json (if present) for related nodes

If any of these already exist, list them with paths before proceeding.

3. Classify

Pick exactly one classification:

Type Signal Default action
Rehouse / IA change "Move X from Y to Z", "rename", "redesign page" Components/hooks/APIs exist. Move/relabel, don't rebuild.
Refactor / Consolidation "Unify X and Y", "deprecate", "single source of truth" Pick canonical path, migrate others, delete the losers.
Extension "Add X to existing Y" New code is the increment, not the system.
Net-new feature No precedent in the platform Justify why it doesn't fit an existing pattern.

4. Surface ambiguity

If anything is unclear, ask before estimating. Examples:

  • "PRD says 'build the Reports page' — I see frontend/components/activity/activity-reports.tsx. Is the PRD adding to it or replacing it?"
  • "There are 3 things called task_* in the schema. Which one does this touch?"
  • "The PRD reads like a config dial — should this be a setting, not a new code path?"

Read the full file on GitHub · 81 lines

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 · 81 lines · 47 tokens per session scan A efa8781956fc

Subscribe to this mod's changes

prd-classify is a skill published in the GitHub repository AutomatosAI/automatos-ai (74 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 907 once invoked, about $0.0002 per session on Opus 5.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-30.

Related

Other skills, from other repositories

knowledge-org

A guide to organising large bodies of knowledge so an AI system can navigate relationships, summaries, and layers instead of searching only flat text chunks. It covers tree indexes, knowledge graphs, file-like structures, incremental updates, and long-term memory layouts.

bojieli/ai-agent-book · 96 tokens

rag-pipeline

A guide to RAG, a method where a system retrieves relevant passages from an external knowledge base before an AI model writes an answer. It covers splitting documents, searching by meaning or exact words, combining results, and measuring retrieval quality.

bojieli/ai-agent-book · 125 tokens

setup-open-index

Install and configure Open Index as the read/write context layer for a domain-specialized agent. Use when setting up a legal, marketing, customer support, sales, infrastructure, or other domain agent with Open Index over MCP.

DrDroidLab/open-index · 48 tokens

remake-deck

Remake a company's source pitch deck (PDF, PPTX, or folder of slide images) into N clean-room design variants that play in the DidiDecks Scroll-UI shell. The agent takes the VP Eng / orchestrator role and runs the dididecks-ai plan Remake-Source-Deck-into-Design-Variants, which extracts and audits the deck, fans out N…

lossless-group/lossless-agent-skills · 290 tokens

go4

Use when designing, architecting, planning, or debugging any system with an LLM in it — agents, agent loops, RAG and retrieval, prompt pipelines, multi-agent or subagent orchestration, tool use and MCP, memory and context management, evals, or production guardrails. Trigger BEFORE committing to an approach — choosing…

jlldavies/go4-llm-design-patterns · 141 tokens

rag-pipelines

Best practices for Retrieval-Augmented Generation (RAG) pipelines. Use when working with vector databases, embeddings, chunking strategies, semantic search, or hybrid search architectures.

neverinfamous/memory-journal-mcp · 38 tokens