Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/cabaynes/charles-claude-skills/newproject)<a href="https://agentmods.dev/skills/cabaynes/charles-claude-skills/newproject"><img src="https://agentmods.dev/badge/skills/cabaynes/charles-claude-skills/newproject/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.
<a href="https://agentmods.dev/skills/cabaynes/charles-claude-skills/newproject"><img src="https://agentmods.dev/badge/skills/cabaynes/charles-claude-skills/newproject.svg" alt="Reviewed on agentmods" width="80" 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.00101 | $0.03414 |
| Opus 5 | $0.00051 | $0.01707 |
| Sonnet 5 | $0.00020 | $0.00683 |
| Haiku 4.5 | $0.00010 | $0.00341 |
Grade A, and why
newproject 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 2d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/newproject — Bootstrap or finish setting up a workspace project
The user wants to start a project under their workspace directory $WORKSPACE_DIR (default ~/projects/). The folder may not exist yet OR it may already exist with partial setup (e.g., they did mkdir $WORKSPACE_DIR/foo and code $WORKSPACE_DIR/foo already). Your job: detect what's in place and create only what's missing — never overwrite existing user content.
What ends up created
$WORKSPACE_DIR/<name>/— empty project directory$WORKSPACE_DIR/<name>/CLAUDE.md— starter project documentation (stub)~/.claude/projects/<project-slug>/memory/— memory dir (with universal-symlink fan-out if afanout-memory.shhelper exists in$WORKSPACE_DIR/scripts/)- Optional:
$WORKSPACE_DIR/<name>/.git/— initialized git repo with sensible.gitignore - Optional: a GitHub repo (private by default) with
originset and a bootstrap commit pushed — plus any web-session skills copied into$WORKSPACE_DIR/<name>/.claude/skills/if your workspace keeps ascripts/web-skills/source (private repos only) - Optional: updated
$WORKSPACE_DIR/CLAUDE.md— if an umbrella file exists with a## Subprojectssection, append an entry
Step 1 — Resolve WORKSPACE_DIR
Check the env var:
echo "${WORKSPACE_DIR:-}"
- If set, use that path (expand
~if present). - If unset, ask the user once via
AskUserQuestion:"WORKSPACE_DIR isn't set. Default is
~/projects/. Use that, or specify a different path?" Options:Use ~/projects/|Use a different path(free-text) - After resolution, recommend (don't enforce) that the user export it in their shell rc so they don't have to set it each session.
For the rest of this skill, $WORKSPACE_DIR is the resolved absolute path (e.g. /Users/alice/projects).
Step 2 — Get the project name and one-line description
If the user provided a name as an argument, use it. Otherwise ask:
"What's the project name? (lowercase, hyphens for spaces, no special characters — e.g.,
tax-tracking,family-recipes)"
What ships with it
2 files 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.
- 2d ago Changed 256efe1dffb4
- 10d ago First seen · 296 lines · 101 tokens per session scan A 025baaf85e28
newproject is a skill published in the GitHub repository cabaynes/charles-claude-skills (1 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 3,414 once invoked, about $0.0005 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
ensemble-solving
Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
code-execution
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
code-refactor
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
code-transfer
Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.
feature-planning
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
review-implementing
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.