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 floomhq/moto --skill new-projectgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/new-project)<a href="https://agentmods.dev/skills/floomhq/moto/new-project"><img src="https://agentmods.dev/badge/skills/floomhq/moto/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.00069 | $0.00739 |
| Opus 5 | $0.00034 | $0.00369 |
| Sonnet 5 | $0.00014 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Project Skill
Step 1: Gather requirements
Ask (if not already clear):
- Project name (kebab-case)
- Tech stack: Next.js / Python FastAPI / Python CLI / Static HTML
- Deploy target: Vercel / Render / Docker / None
- Needs database? (Supabase / Postgres / SQLite)
- Needs auth?
- Needs payments?
Step 2: Create the repo
# ALWAYS private by default
gh repo create <owner>/<name> --private --clone
cd <name>
Step 3: Scaffold by stack
Next.js (most common)
pnpm create next-app . --typescript --tailwind --eslint --app --src-dir --import-alias "@/*"
Python FastAPI
python -m venv .venv
source .venv/bin/activate
pip install fastapi uvicorn python-dotenv
cat > main.py << 'EOF'
from fastapi import FastAPI
app = FastAPI()
@app.get("/api/health")
def health():
return {"status": "ok"}
EOF
cat > requirements.txt << 'EOF'
fastapi==0.115.0
uvicorn==0.32.0
python-dotenv==1.0.1
EOF
Python CLI
python -m venv .venv
# Add entry_points to pyproject.toml
Step 4: Create project CLAUDE.md
Every project gets a CLAUDE.md in root with:
- Project description and purpose
- Tech stack
- Key commands (dev, build, test, deploy)
- Architecture notes
- Known gotchas
Step 5: Environment setup
# Create .env.example (tracked) with placeholder keys
# Create .env.local (gitignored) with real values
echo ".env.local" >> .gitignore
echo ".env" >> .gitignore
NEVER commit real secrets. Only .env.example with placeholders.
Step 6: Git setup
cat >> .gitignore << 'EOF'
node_modules/
.next/
.env
.env.local
.env.production
__pycache__/
.venv/
*.pyc
.DS_Store
WORKPLAN-*.md
EOF
git add -A
git commit -m "Initial scaffold"
git push -u origin main
Step 7: Platform setup (if applicable)
Vercel
vercel link --token $VERCEL_TOKEN
# Set env vars in Vercel dashboard
Supabase
supabase init
supabase link --project-ref <ref>
Checklist before done
- Repo is PRIVATE on GitHub
- .gitignore covers secrets and build artifacts
- CLAUDE.md exists in project root
- .env.example has placeholder keys
- .env.local has real keys (gitignored)
- Build passes locally
- First commit pushed
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.
- 7d ago First seen · 127 lines · 69 tokens per session scan A b7485c71a8cd
new-project is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 739 once invoked, about $0.0003 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-30.
Other skills, from other repositories
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
investigate
Systematic root-cause debugging: find the cause before writing any fix.