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.
npx skills add cboone/agent-harness-plugins --skill scaffold-new-repogit clone --depth 1 https://github.com/cboone/agent-harness-pluginsWrote 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/cboone/agent-harness-plugins/scaffold-new-repo)<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.
<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>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.00179 | $0.02173 |
| Opus 5 | $0.00089 | $0.01086 |
| Sonnet 5 | $0.00036 | $0.00435 |
| Haiku 4.5 | $0.00018 | $0.00217 |
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 8d 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 — 215 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
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.mdh1 heading, not from the directory or branch name (those are often misleading, e.g. worktree paths). Detection order:git remote get-url origin-- extract the repo name from the URL (strip the trailing.gitif 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.- If there is no usable remote, check for an existing
README.mdand use its h1 heading (converted to kebab-case) - 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
.gitignorefirst (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.workor*.test→ Go CLI or Go librarynode_modules/→ JavaScript__pycache__/or*.pyc→ Python*.gemor.bundle/→ Ruby*.ppuor*.compiled→ Pascalxcuserdata/alone, or both.build/and*.ipatogether → Swift.zig-cache/orzig-out/→ Zig CLItarget/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
.gitignoredoes not make it clear.
- Project type options: Go CLI, Go library, JavaScript, Pascal, Python, Ruby, Rust, Shell, Swift, Zig CLI, Generic
What ships with it
6 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.
- 8d ago First seen · 215 lines · 179 tokens per session scan A 12e51855d136
scaffold-new-repo is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed today), licensed MIT. It adds 179 tokens to every session and 2,173 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
gsd-pause-work
Create context handoff when pausing work mid-phase.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
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.