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.
npx skills add ShipWithAI/shipwithai-plugins --skill new-projectgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/skills/shipwithai/shipwithai-plugins/new-project)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/new-project"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/new-project.svg" alt="Measured on agentmods" 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.00078 | $0.02621 |
| Opus 5 | $0.00039 | $0.01311 |
| Sonnet 5 | $0.00016 | $0.00524 |
| Haiku 4.5 | $0.00008 | $0.00262 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/new-project
Greenfield entry point. Guides from an empty directory to a scaffolded project with a configured Claude harness.
Prerequisite Check
Scan for stack indicator files before anything else:
package.json pom.xml build.gradle go.mod Cargo.toml
pyproject.toml Gemfile composer.json mix.exs
If any found:
"This directory already has a project. Use
/shipwithai-starter:initinstead." → stop
Overview
3 phases, each ending with a confirmed artifact. User can redirect at any checkpoint.
Phase 1 → confirm tech stack
Phase 2 → confirm architecture + folder structure
Phase 3 → confirm conventions → final preview → execute
Phase 1 — Project Goals
Ask 5 questions, one per message. Do not bundle questions.
Q0: What's the project name? (used for scaffold command and CLAUDE.md)
"What should we call this project? (e.g. my-app, acme-api)"
Q1: What are you building?
"What type of project is this?"
- Web app
- REST API
- Mobile backend
- CLI tool
- Library
Q2: Who will use it?
"Who's the primary audience for this project?"
- Just me (personal / internal tool)
- Small team or customers (< 1k users)
- Product with real growth targets
Q3: Any hard constraints? (free text, or "none")
"Any constraints I should know? e.g. must use a specific language, existing database to integrate with, specific hosting (Vercel, AWS, self-hosted)."
Q4: One-line description of what the project does. (free text)
After Q4, generate and show a tech stack recommendation:
Based on your answers, I recommend:
Project: [name]
Type: [web app / REST API / mobile backend / CLI / library]
Language: [language]
Framework: [framework + version]
Database: [database]
Hosting: [hosting]
Why: [2-3 sentence reasoning grounded in their specific answers]
Use this stack? (yes / swap one thing / different direction)
| Response | Action |
|---|---|
yes |
Proceed to Phase 2 with confirmed stack |
swap one thing |
"What would you like to swap?" → regenerate recommendation |
different direction |
Return to Q1 |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 317 lines · 78 tokens per session scan A 3b94f625e36c
new-project is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 24d ago), licensed MIT. It adds 78 tokens to every session and 2,621 once invoked, about $0.0004 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.
Other skills, from other repositories
beads-schema
Beads (bd CLI) reference — issue types, statuses, priorities, dependencies, and common commands.
Status
Pipeline dashboard — current feature, position, per-group progress, approvals, pending PRs, blockers. Read-only, any time.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.