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 rules/zigrivers/scaffold/cursorgit clone --depth 1 https://github.com/zigrivers/scaffoldWhat 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 | $0.00049 | $0.00259 |
| Opus 5 | $0.00024 | $0.00130 |
| Sonnet 5 | $0.00010 | $0.00052 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
cursor 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 yesterday.
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.
What it actually says
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.
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.
- yesterday First seen · 21 lines · 49 tokens per session scan A 00197735379e
cursor is a cursor rule published in the GitHub repository zigrivers/scaffold (5 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 259 once invoked, about $0.0002 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 cursor rules, from other repositories
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-asdd
ASDD contribution rules for this repository.
react-composition-patterns
React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
researcher
Researcher agent.
nextjs
Cursor rule "nextjs" from devridge0/basilic-evm, covering next.js rules, core principles, key conventions, component architecture and data fetching.