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 skills add wahidyankf/ose-public --skill specs-scaffoldinggit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/specs-scaffolding)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/specs-scaffolding"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/specs-scaffolding/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/skills/wahidyankf/ose-public/specs-scaffolding"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/specs-scaffolding.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.00046 | $0.00386 |
| Opus 5.5 | $0.00018 | $0.00154 |
| Sonnet 5.5 | $0.00009 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
specs-scaffolding 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.
What it actually says
Scaffolding New Spec Areas
Overview
specs-maker creates new spec areas, missing READMEs, and Gherkin feature structure at
explicitly specified paths under specs/ — never deciding what should exist, only building what
the caller names, following the logical owner corpus shape.
Reference Modules
- surface-profile-trees.md — the four surface-profile directory trees (full-stack, web-only, cli-only, multi-cli) and when each folder is created
- content-generation.md — README inference, Gherkin feature file generation, C4 Mermaid diagram generation
- conventions.md — the PM-readability contract, feature file placement rules, README structure, background steps by surface, folder listing order
Core Principles
- Explicit target only. Creates content only at the caller-specified path(s) — never decides which spec areas should exist, never creates content elsewhere.
- Only scaffold what the surface profile needs. Empty folders are never pre-created; a
cli-only app gets no
components/web/. - Follow established patterns, no novel structures. Every generated file matches the conventions in reference module 03.
Related Agents
specs-checker (validates existing specs — different lifecycle stage), specs-fixer (fixes
existing specs — different lifecycle stage).
What ships with it
5 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.
- 2d ago First seen · 37 lines · 46 tokens per session scan A f1471c49201f
specs-scaffolding is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 386 once invoked, about $0.0002 per session on Opus 5.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-10-14.
Other skills, from other repositories
opengeni-presentations
Create, inspect, edit, import, and export durable Opengeni presentation artifacts and explicit PPTX file boundaries. Use for decks, slides, masters, layouts, rich text, tables, charts, imported media, groups, notes, and visual presentation QA.
opengeni-spreadsheets
Create, inspect, calculate, edit, import, and export durable Opengeni spreadsheet artifacts and explicit XLSX/CSV file boundaries. Use for workbooks, formulas, analyses, tables, calculations, and spreadsheet visual QA. Do not use for controlling a live Excel application.
modern-tooling
Opinionated tooling and conventions for modern JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier, monorepos, library publishing, or establishing coding standards.
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.
walkeros-testing-strategy
Use when writing tests, reviewing test code, or discussing testing approach for walkerOS packages. Covers env pattern, dev examples, and package-specific strategies.