What is scaffold-new-repo?

A project starter that creates the standard foundation for a new repository and adapts it to common project types such as Go, Python, Rust, or JavaScript.

Use it to bootstrap a new project with a license, README, changelog, ignore rules, configuration files, and a plans directory.

It saves time spent deciding which basic files and agent instructions every new repository needs.

scaffold-new-repo — Skill for Claude Code by cboone

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 cboone/agent-harness-plugins --skill scaffold-new-repo

Clone the repo

git clone --depth 1 https://github.com/cboone/agent-harness-plugins

Made for: Claude Code.

Or install scaffold-new-repo, the plugin that ships this one along with the rest of its 1 skill.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/scaffold-new-repo/github.svg)](https://agentmods.dev/skills/cboone/agent-harness-plugins/scaffold-new-repo)

Your own site

<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/scaffold-new-repo"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/scaffold-new-repo/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/scaffold-new-repo"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/scaffold-new-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,107 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.02107
Opus 5.5	$0.00023	$0.00843
Sonnet 5.5	$0.00011	$0.00421
Haiku 4.5	$0.00006	$0.00211

Measured 15d ago against content hash 4470d651ab60, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scaffold-new-repo 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 15d 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.

plugins/scaffold-new-repo/skills/scaffold-new-repo/SKILL.md · 209 lines

How it starts

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

Scaffold New Repo

Generate the language-agnostic foundation files that every new repository starts with.

Workflow

For a community-files request or a parent workflow's community-files mode, run only ./references/community-files/workflow.md to add or update CONTRIBUTING, CODE_OF_CONDUCT, SECURITY and the PR template. Skip foundation files. During full scaffolding, offer this optional workflow after generating foundation files.

1. Gather Project Information

If the user provided a project name in their request, use it directly instead of detecting from git remote or README. If they specified a project type (one of go-cli, go-library, javascript, pascal, python, ruby, rust, shell, swift, zig-cli, generic), use it instead of inferring from .gitignore. Any remaining parameters should still be gathered normally.

Derive what you can automatically, then ask for only what's missing:

Project name -- derive from the git remote URL or README.md h1 heading, not from the directory or branch name (those are often misleading, e.g. worktree paths). Detection order:
1. git remote get-url origin -- extract the repo name from the URL (strip the trailing .git if present, take the last path segment). If the command exits non-zero, returns empty output, or the URL cannot be parsed into a repo name, treat this as "no remote" and continue to step 2.
2. If there is no usable remote, check for an existing README.md and use its h1 heading (converted to kebab-case)
3. Only if both the remote and README detection fail, ask the user for the project name
Short description -- ask the user for a one-sentence description.
Project type -- check the existing .gitignore first (GitHub often generates one when creating the repo). Infer the project type from its contents: Check heuristics in the order listed below. The first match wins.
- go.work or *.test → Go CLI or Go library
- node_modules/ → JavaScript
- __pycache__/ or *.pyc → Python
- *.gem or .bundle/ → Ruby
- *.ppu or *.compiled → Pascal
- xcuserdata/ alone, or both .build/ and *.ipa together → Swift
- .zig-cache/ or zig-out/ → Zig CLI
- target/ with no other language markers matched → Rust
- Minimal or macOS-only entries → Shell or Generic
- Only ask the user for the project type if the .gitignore does not make it clear.
Project type options: Go CLI, Go library, JavaScript, Pascal, Python, Ruby, Rust, Shell, Swift, Zig CLI, Generic

Read the full file on GitHub · 209 lines

Files

What ships with it

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

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.

15d ago Changed · +3 lines · +17 tokens per session 4470d651ab60
1mo ago Changed · -9 lines · -139 tokens per session f977f14cc391
1mo ago First seen · 215 lines · 179 tokens per session scan A 12e51855d136

Subscribe to this mod's changes

scaffold-new-repo is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 2,107 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Claude Code Commits Git and workflow Project management claude code style code-style-guide hooks macos

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

gait-session-tracking

GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.

automateyournetwork/netclaw · 62 tokens

scaffold-new-repo