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-initgit 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-init)<a href="https://agentmods.dev/skills/grojof/ai-workspace-generator/aiws-sdd-init"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-init/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-init"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-init.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.00053 | $0.00452 |
| Opus 5 | $0.00026 | $0.00226 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
aiws-sdd-init 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 10d 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-init — scaffold the project layout (REASONS mode)
Create the initial folder/file layout for the chosen app profile before any spec or code exists. The
canonical layout map (LAYOUTS.md / STRUCTURE_A.md / STRUCTURE_B.md) is an external reference
(supply your own; not bundled here) — load it on demand for the exact tree.
Pre-flight
- Read the profile (A | B) and capability flags from the
aiws-sdd-onboardingdecision (or ask to run it first). - Refuse if code already exists (non-empty package /
index.html); this skill only bootstraps an empty repo.
What it writes
- Profile A (Python):
pyproject.toml(uv) ·src/<package>/{domain,application,infrastructure,interfaces}/·tests/{unit,integration,e2e}/+conftest.py·config.py. App object exported as<package>.interfaces.api:app. - Profile B (HTML+JS):
index.html(CSP meta) ·js/(orsrc/for bundled/react/node-server) ·css/·tests/smoke.test.html. Build/npm only whenuses_npm_build/uses_react/runs_node_server.
Store & next step
Specs live in {{paths.specs}}/, in-flight work in {{paths.changes}}/<change>/ — both versioned in Git (no
_vN suffixes). Record the scaffold decision in the change-folder. Hand off to aiws-sdd-spec-capture.
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.
- 10d ago First seen · 29 lines · 53 tokens per session scan A 6d7c62403ef1
aiws-sdd-init is a skill published in the GitHub repository grojof/ai-workspace-generator (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 452 once invoked, about $0.0003 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…