Borrowing it
Nothing to install: this file belongs to ThoBustos/openyoko. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ThoBustos/openyoko/main/.claude/skills/new-project/SKILL.mdgit clone --depth 1 https://github.com/ThoBustos/openyokoWrote 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/thobustos/openyoko/new-project)<a href="https://agentmods.dev/skills/thobustos/openyoko/new-project"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/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.00000 | $0.02447 |
| Opus 5 | $0.00000 | $0.01223 |
| Sonnet 5 | $0.00000 | $0.00489 |
| Haiku 4.5 | $0.00000 | $0.00245 |
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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/new-project Skill
Create a new project with a structure tailored to what you'll actually do.
Usage
/new-project [name]
Examples:
/new-project- Interactive flow to create a project/new-project health-app- Create project with specified name
Prerequisites
Before running this skill, check:
-
GLOBAL_STATE.md exists - Check
00_SYSTEM/GLOBAL_STATE.md- IF MISSING: "Your vault isn't set up yet. Would you like to run /onboarding first?"
-
03_PROJECTS/ folder exists
- IF MISSING: Create it
Philosophy: Description-Driven Structure
Every project is different. A client business has different needs than a podcast, which is different from a personal health project.
Instead of asking "what type is this?", we ask "what will you DO in this project?" and propose folders based on signals in your description.
Flow
Step 1: Gather Core Project Information
Ask (if not provided):
- "What's the project name?" (will be used for folder name)
Then ask:
- "Describe this project in 1-2 sentences. What will you DO here? (build, sell, write, manage, track, create...)"
Step 2: Detect Signals & Propose Structure
Parse the description for these signals:
| If description mentions... | Propose folder |
|---|---|
| clients, customers, contracts, proposals, agreements | Legal/, Accounts/, Clients/ |
| team, engineering, code, PRs, technical, build, develop | Engineering/, Reports/ |
| content, podcast, videos, episodes, subscribers, publish | Content/, Episodes/, Metrics/ |
| money, budget, investments, revenue, expenses | Finances/ |
| calls, meetings, 1:1s | Calls/ |
| metrics, growth, KPIs, analytics, tracking | Metrics/ |
| workflows, processes, playbooks, operations | Operations/ |
| community, members, audience, subscribers | Community/ |
| research, learning, notes | Notes/, Research/ |
| diagrams, architecture, design | Diagrams/ |
| writing, drafts, publishing | Drafts/, Published/ |
| people, contacts, relationships | People/ |
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 · 409 lines · 0 tokens per session scan A 45c191547dc0
new-project is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,447 tokens. 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.