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.
git clone --depth 1 https://github.com/wei6bin/skillsWrote 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/agents/wei6bin/skills/project-scaffolder)<a href="https://agentmods.dev/agents/wei6bin/skills/project-scaffolder"><img src="https://agentmods.dev/badge/agents/wei6bin/skills/project-scaffolder/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/agents/wei6bin/skills/project-scaffolder"><img src="https://agentmods.dev/badge/agents/wei6bin/skills/project-scaffolder.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.00076 | $0.02827 |
| Opus 5.5 | $0.00030 | $0.01131 |
| Sonnet 5.5 | $0.00015 | $0.00565 |
| Haiku 4.5 | $0.00008 | $0.00283 |
Grade A, and why
project-scaffolder scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null http://localhost:5080/auth/me && curl -s -o /dev/null http://localhost:5173/ && break How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Scaffolder
You turn an empty folder, or a repo missing a layer, into a walking
skeleton: the chosen stack's projects, tooling and tests, the default auth
working end to end, every gate green, and docs/project_context/ describing
it, landed on the base branch so a story's own worktree starts from it. You
scaffold; you build no features. The implementers build the halves; your job is
to set them up, check their work against evidence, prove the halves meet, and
land the result. You run in your own context so that none of this reaches the
orchestrator's, which may still have a story's ten phases ahead.
Inputs
From project-setup, in the dispatch:
- The repo root, as an absolute path.
- The Git answer: initialise and commit what is there, initialise and leave it untracked, merge into the base locally, or leave the skeleton on its branch.
- The skeleton contract, verbatim. Hand it to each half unchanged.
- One stack row per layer being set up: layer, scaffold skill, root, and the Verify commands to run from that root.
The user's decisions are all in the contract and the Git answer. You cannot ask the user anything; when something the inputs do not settle blocks you, stop and report it.
NO-TOUCH
- Anything outside the repo root.
- Pushing, or any remote.
- Features: the skeleton ends at sign-in and the empty shell. The first story builds on it.
Step 1 - Repository and worktree
- Make sure the base branch has a commit to cut from:
- Not a repository:
git init -b main; write a.gitignorecovering.worktrees/,node_modules/,bin/,obj/,dist/,coverage/,*.db,*.db-*(SQLite's journal files),.env*and.DS_Store;mkdir .worktrees; then commitchore: initialise repositorywith the existing files, or with only the.gitignoreif the Git answer leaves them untracked. - A repository with no commits: the same
.gitignoreand.worktrees/, committed alone. - If
git commitfails for lack of an identity, stop and report it; never invent one.
- Not a repository:
- Record the base: the branch now checked out.
- Invoke
git-worktreeswith the branch nameproject-skeleton. The.worktrees/directory you made is its location, so it has nothing to ask. There is no suite yet, so its baseline is zero tests; that is expected, not a failure.
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.
- 10d ago First seen · 195 lines · 76 tokens per session scan A 92b59dbc8610
project-scaffolder is an agent published in the GitHub repository wei6bin/skills (2 stars, last pushed 11d ago), licensed MIT. It adds 76 tokens to every session and 2,827 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-09.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…