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/komluk/scaffolding/spec-developnpx skills add komluk/scaffolding --skill spec-developgit clone --depth 1 https://github.com/komluk/scaffoldingWhat 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.00858 |
| Opus 5 | $0.00024 | $0.00429 |
| Sonnet 5 | $0.00010 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
spec-develop 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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Apply (Task Execution)
Guide for implementing code changes driven by tasks.md.
Input Files
| File | Purpose | Action |
|---|---|---|
{specs_path}/tasks.md |
Implementation checklist | Read, execute, mark done |
{specs_path}/design.md |
Architecture decisions | Reference during implementation |
{specs_path}/proposal.md |
Context and motivation | Reference if unclear on intent |
Path Enforcement: The specs_path MUST be .scaffolding/conversations/{UUID}/specs/ where {UUID} is a valid UUID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). NEVER use descriptive folder names.
Execution Protocol
Step 1: Read tasks.md
Parse all task groups and checkboxes. Identify dependency order.
Step 2: Execute tasks in order
For each task (- [ ] N.M description):
- Read the task description and target file path
- Check design.md for relevant requirements and decisions
- Implement the change following project patterns
- Mark complete: change
- [ ]to- [x]
Step 3: Run validation after each group
| Stack | Validation Command |
|---|---|
| Backend | pytest |
| Frontend | npm run validate |
| Both | Run both commands |
Step 4: Handle blockers
If a task cannot be completed:
- [ ] 2.3 Implement caching layer
> BLOCKED: Redis connection config not yet available. Depends on devops setup.
Continue with unblocked tasks. Do not stop the entire chain.
Rules
| Rule | Detail |
|---|---|
| Execute in order | Respect dependency sequence |
| Mark progress | - [ ] -> - [x] as you complete |
| Reference design | Check design.md before implementing |
| Never modify specs | Only modify tasks.md checkboxes, never change spec content |
| Validate per group | Run tests after each task group |
| Note blockers | Add > BLOCKED: note, skip and continue |
| Search before write | Check core/utils/, core/exceptions.py before creating helpers |
Progress Tracking
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.
- 2d ago First seen · 106 lines · 49 tokens per session scan A f9e6f56ec861
spec-develop is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 26d ago), licensed MIT. It adds 49 tokens to every session and 858 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-30.
Other skills, from other repositories
ideogram-ultra
Build Ideogram 4 (Ideogram Ultra) txt2img and img2img workflows with the local open-weights model, dual conditional/unconditional models with DualModelGuider, Qwen3-VL text encoder, and structured JSON ("compositional deconstruction") prompts for strong text rendering and layout control.
model-compatibility
Model family compatibility matrix covering loaders, resolutions, samplers, CFG, VAE, ControlNet, and LoRA compatibility for SD 1.5, SDXL, Flux, SD3, and video models.
panel-node-pack-sync
Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (installcomfyui (action:"selfupdate"), npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way…
civitai
Discover Civitai models with the BUILT-IN downloadmodel action:"searchcivitai" and install/generate them locally. Find a checkpoint/LoRA/embedding on Civitai, download it into ComfyUI, and use its trigger words. Optionally pair the official Civitai MCP for community features (images browsing, posting, collections).
31-offer-design-global
Use when the WHAT being sold needs work, not the price and not the copy — core promise, value stack, bonuses, guarantee and risk reversal, honest scarcity and urgency, tier packaging, upsell and downsell paths, and high-ticket or productized service structures. Trigger on 'design an offer', 'irresistible offer'…
aeo-geo
Strategy module for Answer Engine / Generative Engine Optimization — audits AI visibility, restructures content for citation, runs entity-consistency checks across Knowledge Graph, Wikidata, Wikipedia, Crunchbase, and LinkedIn, and produces JSON-LD schema specs, monitoring frameworks, and a 90-day LLM content…