Borrowing it
Nothing to install: this file belongs to abuango/pos-ai. 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/abuango/pos-ai/main/.claude/skills/project-creation/SKILL.mdgit clone --depth 1 https://github.com/abuango/pos-aiWrote 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/abuango/pos-ai/project-creation)<a href="https://agentmods.dev/skills/abuango/pos-ai/project-creation"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/project-creation.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.00041 | $0.00656 |
| Opus 5 | $0.00020 | $0.00328 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
project-creation 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Creation Skill
Setup
Before starting: check .handoff/sessions/ for active sessions, read context status.yaml, run git status. Follow .rules/universal.md (Plan -> Approve -> Execute).
Create and initialize new projects with full setup.
Commands
/project create {team} {name}- Create a new project/project list {team}- List team projects/project status {team} {project}- Show project status
/project create {team} {name}
Required: Team name, project name (kebab-case), description, type (internal/client), tech stack, priority, git remote.
Steps
- Validate team:
ls {teams_dir}/{team}/team.yaml - Clone or init repo in
{teams_dir}/{team}/repos/ - Create project directory:
mkdir -p {teams_dir}/{team}/projects/{name}/{plans,reviews,logs} - Create project YAML at
{teams_dir}/{team}/projects/{name}.yaml:name: "{name}" description: "{description}" type: internal | client team: "{team}" workspace: "{teams_dir}/{team}/repos/{name}" status: new # new | planning | active | review | complete | on_hold priority: medium created: "{today}" repository: host: gitlab.example.com path: "{gitlab_path}" active_branch: main deployment: platform: "" # e.g., dokploy, vercel, railway project_id: "" services: [] requirements: [] acceptance_criteria: [] history: - date: "{today}" action: "Project created" by: cto - Add to platform registry - Edit
pos.yamlunderteams.{team}.repos - Update team config - Add to
active_projectsinteam.yaml, assign port - Generate PROJECT_INDEX.yaml:
./scripts/generate-project-index.sh {name} {team} - Optional: Create initial sprint in
plans/sprints/
Status Flow
new -> planning -> active -> review -> complete
|
on_hold
Output
Report: project file path, repo location, GitLab URL, files created, next steps (clone repo, create sprint, start session).
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 · 75 lines · 41 tokens per session scan A 490caa1a8d99
project-creation is a skill published in the GitHub repository abuango/pos-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 656 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.
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.