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/odinmb/ops-workflow/scaffoldnpx skills add OdinMB/ops-workflow --skill scaffoldgit clone --depth 1 https://github.com/OdinMB/ops-workflowWhat 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.00030 | $0.02137 |
| Opus 5 | $0.00015 | $0.01069 |
| Sonnet 5 | $0.00006 | $0.00427 |
| Haiku 4.5 | $0.00003 | $0.00214 |
Grade A, and why
scaffold 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 3d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ops Scaffold
Set up a new non-code project management repo, or adjust an existing one to match the ops conventions.
Detect Mode
Check the current directory:
- If
CLAUDE.mdexists → Adjust mode: read it, compare against the template below, and propose specific changes. Don't overwrite — use Edit to patch. Ask before creating missing folders. - If no
CLAUDE.md→ New repo mode: run the full interview and scaffold from scratch.
Interview (New Repo Mode)
Ask the user:
- Project name — what the project is called
- One-paragraph description — what the project does, who it's for
- Constraints — team size, budget, timeline, key limitations
- Goals — 2-4 strategic goals for the near term
- Initial domain areas — what topics will the project cover? These become the initial subfolders. Examples:
- Marketing, legal, fundraising, partnerships, technical research
- Or more specific: grants, audience growth, competitor analysis
- Connected to a coding repo? — ask if this ops repo is paired with a codebase. If yes, ask for the relative path from this repo to the code repo root (e.g.,
../if sibling directories,../app/if nested). This enables read-only access to the code for context.
Interview (Adjust Mode)
Read the existing structure (CLAUDE.md, MEMORY.md, folder listing). Then ask:
- What needs changing? — or just check against the template and propose fixes
- Missing folders? — offer to create any missing standard folders with INDEX.md files
- CLAUDE.md drift? — show specific differences from the template and offer to patch
Directory Structure
<project-dir>/
├── .claude/
│ └── settings.json
├── state/
│ └── INDEX.md
├── backlog/
│ └── INDEX.md
├── references/
│ └── INDEX.md
├── artifacts/
│ └── INDEX.md
├── plans/
│ ├── INDEX.md
│ └── completed/
│ └── INDEX.md
├── .update/
│ └── .gitkeep
├── .gitignore
├── CLAUDE.md
└── MEMORY.md
For each domain area the user specified, create a subfolder with an INDEX.md in the appropriate parent:
- Research topics → subfolders under
references/ - Task areas → subfolders under
backlog/ - Only create
state/subfolders if the user has multiple distinct state areas
What ships with it
2 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.
- 3d ago First seen · 275 lines · 30 tokens per session scan A 19dde148df95
scaffold is a skill published in the GitHub repository OdinMB/ops-workflow (7 stars, last pushed 16d ago), licensed MIT. It adds 30 tokens to every session and 2,137 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 skills, from other repositories
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-full-auto
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
factory-db-migration
The operational discipline for running a destructive change against a production database — schema migrations, data backfills, one-shot RPCs, historical seed imports. Adjacent to factory-data-layer.md (schema design) and factory-deployment.md (where migrations execute in CI) — this skill is about the runbook around…
people-intel
This skill should be used when the user asks to 'research person', 'person intel', 'people intel', 'who is [person]', 'who created [project]', 'who maintains [package]', 'add person to knowledge graph', 'enrich person note', 'update person note', 'document [person]', 'create person note for [name]'. Researches a…
schema-evolve
This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…
dev-cycle
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.