pos-ai: Skill for Claude Code

.claude/skills/project-creation/SKILL.md

project-creation is a skill for Claude Code from abuango/pos-ai. It costs 41 tokens per session (656 once invoked), scanned A, original, MIT.

A project setup workflow for creating project records and their supporting folders in a team-based project tracking system.

In plain words
What is it for?
Use it to start a project, initialize project tracking, create its repository workspace, and record details such as its team, type, technology, priority, and status.
Why use it?
It removes the need to create project files, directories, repository links, and initial tracking details by hand.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is abuango/pos-ai's own configuration. It tells Claude Code how to work on pos-ai itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pos-ai configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/abuango/pos-ai/main/.claude/skills/project-creation/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/abuango/pos-ai

Made for: Claude Code.

Wrote 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.

agentmods badge for project-creation

README.md
[![agentmods](https://agentmods.dev/badge/skills/abuango/pos-ai/project-creation.svg)](https://agentmods.dev/skills/abuango/pos-ai/project-creation)
Your own site
<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>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 656 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 490caa1a8d99, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.claude/skills/project-creation/SKILL.md · 75 lines

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

  1. Validate team: ls {teams_dir}/{team}/team.yaml
  2. Clone or init repo in {teams_dir}/{team}/repos/
  3. Create project directory: mkdir -p {teams_dir}/{team}/projects/{name}/{plans,reviews,logs}
  4. 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
    
  5. Add to platform registry - Edit pos.yaml under teams.{team}.repos
  6. Update team config - Add to active_projects in team.yaml, assign port
  7. Generate PROJECT_INDEX.yaml: ./scripts/generate-project-index.sh {name} {team}
  8. 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).

Read the full file on GitHub · 75 lines

Files

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.

Changes

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.

  1. 6d ago First seen · 75 lines · 41 tokens per session scan A 490caa1a8d99

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

specstoryai/getspecstory · 126 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

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.

wshobson/agents · 54 tokens