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 agentmods add skills/zigrivers/scaffold/scaffold-pipelinenpx skills add zigrivers/scaffold --skill scaffold-pipelinegit clone --depth 1 https://github.com/zigrivers/scaffoldWrote 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/zigrivers/scaffold/scaffold-pipeline)<a href="https://agentmods.dev/skills/zigrivers/scaffold/scaffold-pipeline"><img src="https://agentmods.dev/badge/skills/zigrivers/scaffold/scaffold-pipeline.svg" alt="Measured on agentmods" 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.00054 | $0.03749 |
| Opus 5 | $0.00027 | $0.01875 |
| Sonnet 5 | $0.00011 | $0.00750 |
| Haiku 4.5 | $0.00005 | $0.00375 |
Grade A, and why
scaffold-pipeline 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 6d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Pipeline Reference
This skill is a static reference for pipeline ordering and dependency constraints. It does NOT handle status checks, progress queries, or navigation.
Activation boundary: If the user asks "where am I?", "what's next?", "pipeline status", or anything about their current progress → do not use this skill. The scaffold-runner skill handles all status/navigation via the scaffold CLI.
Use this skill ONLY when the user asks about:
- Pipeline design: "what phases are there?", "what's the ordering?"
- Dependency rules: "what depends on what?", "can I run X before Y?"
- Step reference: "what commands are in phase 3?", "is design-system optional?"
Run scaffold guides pipeline for the full phase/dependency reference (add
--markdown for the plain-text body), and scaffold next to see which steps are
eligible right now.
Phases
16 phases, each with a slug (used in frontmatter) and display name. Canonical source: src/types/frontmatter.ts PHASES constant.
| # | Slug | Display Name | Description |
|---|---|---|---|
| 0 | vision |
Product Vision | Transforms your idea into a strategic vision document covering who it's for, what makes it different, and what success looks like. |
| 1 | pre |
Product Definition | Translates your vision into a PRD with features, personas, and success criteria, then breaks it into user stories with testable acceptance criteria. |
| 2 | foundation |
Project Foundation | Researches and documents technology choices, creates coding standards with linter configs, defines testing strategy, and designs directory layout. |
| 3 | environment |
Development Environment | Sets up local dev environment, design system (web only), git workflow with CI and worktrees, automated PR review, and AI memory persistence. |
| 4 | integration |
Testing Integration | Auto-detects platform and configures E2E testing — Playwright for web, Maestro for mobile. Skips for backend-only. |
| 5 | modeling |
Domain Modeling | Identifies core concepts (entities, relationships, invariants, events) and establishes a shared vocabulary across all docs and code. |
| 6 | decisions |
Architecture Decisions | Documents every significant design decision with alternatives and consequences, so future contributors know why. |
| 7 | architecture |
System Architecture | Designs the system blueprint — components, data flows, module structure, and extension points. |
| 8 | specification |
Specifications | Creates interface specs: database schema with constraints, API contracts with error codes, UX flows with accessibility. Each conditional. |
| 9 | quality |
Quality Gates | Reviews testing, generates test skeletons, creates eval checks, designs deployment pipeline, and conducts security review. |
| 10 | parity |
Platform Parity | Audits documentation for platform-specific gaps. Skips for single-platform projects. |
| 11 | consolidation |
Consolidation | Optimizes {{INSTRUCTIONS_FILE}} under 200 lines and audits all workflow docs for consistency. |
| 12 | planning |
Planning | Decomposes stories into concrete tasks scoped to ~150 lines and 3 files max, with clear acceptance criteria. |
| 13 | validation |
Validation | Seven cross-cutting audits: scope creep, dependency cycles, implementability, traceability, naming drift, broken handoffs, decision completeness. |
| 14 | finalization |
Finalization | Applies validation findings, freezes docs, creates onboarding guide, and writes the implementation playbook. |
| 15 | build |
Build | Stateless TDD execution: single/multi-agent modes, session resume, quick tasks, and new feature enhancements. |
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.
- 6d ago First seen · 223 lines · 54 tokens per session scan A 65c54a1d3bff
scaffold-pipeline is a skill published in the GitHub repository zigrivers/scaffold (5 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 3,749 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.
Other skills, from other repositories
commands-standards
Standards for authoring SDD plugin commands — frontmatter, user interaction, skill/agent invocation, CLI integration, and output formatting.
agents-standards
Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.
skills-standards
Standards for authoring SDD plugin skills — frontmatter, self-containment, and input/output schemas.
backend-standards
CMDO architecture standards for Node.js/TypeScript backends with strict layer separation.
commit
Create a commit following repository guidelines with proper versioning and changelog updates.
tasks
Manage tasks and plans using the .tasks/ directory.