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 grojof/ai-workspace-generator --skill aiws-sdd-spec-capturegit clone --depth 1 https://github.com/grojof/ai-workspace-generatorWrote 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/grojof/ai-workspace-generator/aiws-sdd-spec-capture)<a href="https://agentmods.dev/skills/grojof/ai-workspace-generator/aiws-sdd-spec-capture"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-spec-capture/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/grojof/ai-workspace-generator/aiws-sdd-spec-capture"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-spec-capture.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.00048 | $0.00504 |
| Opus 5 | $0.00024 | $0.00252 |
| Sonnet 5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
aiws-sdd-spec-capture 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 12d 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
aiws-sdd-spec-capture — guided interview → REASONS spec
Turn a non-technical user's needs into a valid REASONS spec. Ask one focused question at a time in the
user's language (CA/ES/EN); headings/keys stay English (body in the project language). Re-entrant: persist
partial answers in the change-folder so a pause is safe. Schema reference: the aiws-sdd-spec-schema skill.
Flow
- Title +
slug+estimated_complexity(S/M/L) + tags. Nextspec_id= max(existing)+1, 3-digit. - Walk the 8 H1 sections in order (Requirements → Entities → Approach → Structure → Operations →
Norms → Safeguards, plus §0 Changelog). Auto-fill §3/§4/§6/§7 from the profile, flags and conventions;
ask only what the flags imply (auth questions iff
requires_authentication, §7.2 iffhandles_personal_data). - Hard gates: §1.4 ≥1 explicit exclusion; §1.5 ≥3 Given/When/Then; every §5 Operation has a
Maps to:citing ≥1 acceptance criterion; every external call declares an explicit timeout. - UI apps (
serves_html_ui/ Profile B UI): produce a static HTML mockup the user signs off on first. - Validate against the full
aiws-sdd-spec-schemachecklist before writing. Never save an invalid spec.
Write
Write {{paths.specs}}/<NNN>-<slug>.md with status: draft, version: v1. Record the interview summary +
hard decisions in {{paths.changes}}/<change>/. Hand off to spec review (sign-off → user-reviewed).
Does NOT
Generate code or tests; invent answers when a question is open (always ask); touch files outside the spec store and change-folder.
What ships with it
1 file 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.
- 12d ago First seen · 33 lines · 48 tokens per session scan A e40c553a28b7
aiws-sdd-spec-capture is a skill published in the GitHub repository grojof/ai-workspace-generator (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 48 tokens to every session and 504 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…