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.
git clone --depth 1 https://github.com/rianvdm/product-ai-publicWrote 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/commands/rianvdm/product-ai-public/new-project)<a href="https://agentmods.dev/commands/rianvdm/product-ai-public/new-project"><img src="https://agentmods.dev/badge/commands/rianvdm/product-ai-public/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.
<a href="https://agentmods.dev/commands/rianvdm/product-ai-public/new-project"><img src="https://agentmods.dev/badge/commands/rianvdm/product-ai-public/new-project.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.00007 | $0.00465 |
| Opus 5 | $0.00003 | $0.00233 |
| Sonnet 5 | $0.00001 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
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 yesterday.
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.
What it actually says
New Project Scaffolding
Read these files before proceeding:
01-context/project-template.md- REQUIRED: Project brain structure and templates01-context/product-philosophy.md- My product beliefs
Project Description
$ARGUMENTS
Instructions
Create a new project brain folder based on the template in 01-context/project-template.md.
Steps
-
Parse the project description to determine:
- A short, kebab-case folder name (e.g.,
logpush-bigquery,developer-portal) - The full project name for the CONTEXT.md title
- A short, kebab-case folder name (e.g.,
-
Create the folder structure at
work/projects/[project-name]/:[project-name]/ ├── CONTEXT.md ├── artifacts/ ├── decisions/ ├── research/ └── meetings/ -
Generate CONTEXT.md using the template from
01-context/project-template.md:- Fill in the project name
- Set Status to "Discovery"
- Set PM to the project's actual line owner if the description or source material names one (e.g. a specific team PM); otherwise default to "[Author]". When the director/portfolio lead is not the line PM, record the line owner as Project Owner and note the portfolio lead separately.
- Draft a problem statement based on the description provided
- Leave other fields as placeholders for the user to fill in
- Add any obvious open questions based on the description
-
Create placeholder files in subdirectories:
artifacts/.gitkeepdecisions/.gitkeepresearch/.gitkeepmeetings/.gitkeep
-
Report what was created and suggest next steps:
- Fill in the Quick Reference table (Eng Lead, Designer, Target Launch)
- Define success metrics with baselines and targets
- Identify key stakeholders
- Search wiki for related prior work
Before Creating
Search for any existing documentation or prior work related to this project. Mention relevant findings when reporting what was created.
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.
- yesterday First seen · 58 lines · 7 tokens per session scan A c41d36a938c7
new-project is a command published in the GitHub repository rianvdm/product-ai-public (15 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 465 once invoked, about $0.0000 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-09-09.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.