agentmods.dev

aa-new-project

aa-new-project is a skill for Claude Code from Peeyushmeher/agent-agile. It costs 36 tokens per session (909 once invoked), scanned A, original, MIT.

A planning tool for starting a new project in the Agent-Agile system from a clear idea, with questions that turn the idea into an actionable development plan.

In plain words
What is it for?
Use it to clarify the project, research uncertainties, define prerequisites, split epics into smaller stories, and prepare work that developers can pick up.
Why use it?
It exposes missing decisions and risky unknowns before implementation, reducing guesswork about scope, priorities, and how work should be divided.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agent-agile plugin — 11 skills, 11 agents shipped together

not rated 3repo 1mo ago A scan 36 tokens original MIT

Good fit Use it to clarify the project, research uncertainties, define prerequisites, split epics into smaller stories, and prepare work that developers can pick up.

Compare 6 skills from other repositories ↓
View source ↗ Peeyushmeher/agent-agile
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Peeyushmeher/agent-agile
Claude Code
/plugin install agent-agile

Made for: Claude Code.

Or install agent-agile, the plugin that ships this one along with the rest of its 11 skills, 11 agents.

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 aa-new-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-new-project/github.svg)](https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-new-project)
Your own site
<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-new-project"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-new-project/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 aa-new-project

Your own site · 80×15
<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-new-project"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-new-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 909 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.00036 $0.00909
Opus 5 $0.00018 $0.00454
Sonnet 5 $0.00007 $0.00182
Haiku 4.5 $0.00004 $0.00091

Measured 11d ago against content hash 204226088d46, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

aa-new-project 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 11d 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.

skills/aa-new-project/SKILL.md · 36 lines

How it starts

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

aa-new-project

Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.

Read playbooks/planner.md sections The 8 intake questions, Pushback patterns, Drafting the plan, Research fan-out and the risk register, Slicing epics into stories, The worker-readiness test, and Extracting PREREQS, in full, and follow them exactly — do NOT re-derive or improvise the system.

Intake

If .planning/IDEA.md exists, read it and, per planner.md's Grill → intake mapping, confirm the pre-filled answers back to the user instead of re-asking them. Ask only the questions the grill didn't answer, plus the three it never answers (hard constraints, riskiest unknown, review-batch appetite) — always fresh. If IDEA.md does not exist, ask all 8 questions from scratch, one at a time, applying the pushback patterns to every thin answer before moving on.

After the eighth answer and before writing any files, deliver the split statement exactly as defined at the end of planner.md's The 8 intake questions — the "my part / your part" narration plus the process preview. It is a required step, not optional color.

Drafting

Draft the plan inline in this conversation, following Drafting the plan — this is the default; do not spawn a separate agent for this step unless the user asks for it. Produce, in order:

  1. .planning/PROJECT.md from playbooks/templates/PROJECT.md.
  2. .planning/ROADMAP.md from playbooks/templates/ROADMAP.md — every epic, riskiest first, one-line demo sentences; only the current epic (Epic 1) gets full detail.
  3. If the roadmap draft is multi-epic, run Research fan-out and the risk register exactly as written (including its off-ramp): spawn aa-researcher-domain and aa-researcher-ecosystem as parallel fresh subagents with the model configured for the smart tier in .planning/CONFIG.md (ask for tiers now if CONFIG.md doesn't exist yet), synthesize .planning/RESEARCH.md from playbooks/templates/RESEARCH.md, then revise the roadmap draft against the risk register — [fixture: …] tags on epic lines, Epic 1/2 riskiest-first re-examination.
  4. Slice Epic 1 into story cards per Slicing epics into stories, writing each from playbooks/templates/STORY.md — including one fixture story per [fixture: …] tag on Epic 1. Apply The worker-readiness test to every card before calling it done.
  5. .planning/PREREQS.md from playbooks/templates/PREREQS.md per Extracting PREREQS, status pending for every row.
  6. .planning/CONFIG.md from playbooks/templates/CONFIG.md — ask the user for smart_tier, cheap_tier, gate, and commercial if not already set.
  7. .planning/STATE.md from playbooks/templates/STATE.md, Phase intake, pointing at PROJECT.md, ROADMAP.md, and Epic 1's stories.

Read the full file on GitHub · 36 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. 11d ago First seen · 36 lines · 36 tokens per session scan A 204226088d46

Subscribe to this mod's changes

aa-new-project is a skill published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 909 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.

Claude CodePlanningProject managementagent-skillsagileai-agentscodexokr
Related

Other skills, from other repositories

project-manager

This skill has been upgraded with agentic AI capabilities, OKR/KPI integration patterns, and async-first workflows based on 2026 PM best practices research.

buiphucminhtam/forgewright · 68 tokens

github-project-management

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.

ruvnet/RuView · 25 tokens

team-okrs

An OKR tracking page for a quarter. OKRs, or objectives and key results, are goals paired with measurable results.

nexu-io/html-anything · 23 tokens

product-frameworks

Product management frameworks for business cases, market analysis, strategy, prioritization, OKRs/KPIs, personas, requirements, and user research. Use when building ROI projections, competitive analysis, RICE scoring, OKR trees, user personas, PRDs, or usability testing plans.

yonatangross/orchestkit · 61 tokens

gr-product-dev-ops

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified…

Gingiris-1031/gingiris-skills · 576 tokens

github-project-management

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.

ruvnet/ruflo · 25 tokens