client-project-setup

client-project-setup is a skill for Claude Code from hamzaPixl/pixl-ai. It costs 58 tokens per session (688 once invoked), scanned A, original, MIT.

A quick-reference skill for the Caveman tools and commands. Caveman is a set of response modes that changes how briefly and directly the assistant writes.

In plain words
What is it for?
It lists commands for switching between Lite, Full, Ultra, and Wenyan writing modes, plus tools for terse commits, review comments, and compressed responses.
Why use it?
It helps users remember the available modes, related skills, and commands without changing the current mode. The reference also explains how to turn the mode off.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

Part of the pixl-crew plugin — 93 skills, 14 agents, 6 hooks shipped together

Good fit It lists commands for switching between Lite, Full, Ultra, and Wenyan writing modes, plus tools for terse commits, review comments, and compressed responses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzapixl/pixl-ai/client-project-setup
Install

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.

Any agent
npx skills add hamzaPixl/pixl-ai --skill client-project-setup
Clone the repo
git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

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 client-project-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/client-project-setup/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/client-project-setup)
Your own site
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/client-project-setup"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/client-project-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for client-project-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/client-project-setup"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/client-project-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 688 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.00058 $0.00688
Opus 5 $0.00029 $0.00344
Sonnet 5 $0.00012 $0.00138
Haiku 4.5 $0.00006 $0.00069

Measured 9d ago against content hash 82bc15118b46, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

client-project-setup 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 9d 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.

packages/crew/skills/client-project-setup/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Client project onboarding pipeline: scan → catalog → generate CLAUDE.md → create context packet. Uses the onboarding-agent for exploration and produces ready-to-use project documentation.

Required References

Before starting, read references/methodology/client-onboarding.md for the onboarding checklist and CLAUDE.md template.

Step 1: Validate Input

  1. Confirm the project path exists and is a valid directory
  2. Check if a CLAUDE.md already exists (offer to audit/improve instead of overwrite)
  3. Check if .claude/ directory exists

Step 2: Codebase Exploration

Delegate to the onboarding-agent to perform a read-only scan of the project:

Launch onboarding-agent with prompt:
"Scan the project at {path}. Produce a complete onboarding report including:
stack summary, tech stack table, directory map, key files, conventions,
CLAUDE.md draft, and risks/gaps."

Step 3: Generate CLAUDE.md

Delegate to the /claude-md skill to produce the CLAUDE.md. Pass it the onboarding-agent's report as additional context. This avoids duplicating the CLAUDE.md generation logic.

If a CLAUDE.md already exists, use /claude-md in improve mode instead to audit and enhance it.

Step 4: Create Context Packet

Generate a .context/project-overview.md file with:

  1. Stack summary — for sharing with team members
  2. Architecture diagram (ASCII) — high-level component relationships
  3. Dependency map — key external services and integrations
  4. Risk register — technical debt, missing tests, security concerns

Step 5: Setup Recommendations

Based on the scan, recommend:

  1. Missing infrastructure:
    • No CI/CD → suggest GitHub Actions
    • No linting → suggest ESLint/Prettier or Ruff
    • No testing → suggest test framework
    • No Docker → suggest containerization
  2. pixl-crew integration:
    • Which agents are most relevant for this project type
    • Which skills to use first (e.g., /seo-audit for websites, /ddd-pattern for backends)
  3. Quick wins:
    • Easy improvements that can be made immediately

Read the full file on GitHub · 80 lines

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. 9d ago First seen · 80 lines · 58 tokens per session scan A 82bc15118b46

Subscribe to this mod's changes

client-project-setup is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 688 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-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

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

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

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

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens