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-onboardinggit 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-onboarding)<a href="https://agentmods.dev/skills/grojof/ai-workspace-generator/aiws-sdd-onboarding"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-onboarding/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-onboarding"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-onboarding.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.00058 | $0.00755 |
| Opus 5 | $0.00029 | $0.00378 |
| Sonnet 5 | $0.00012 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
aiws-sdd-onboarding 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 11d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aiws-sdd-onboarding — pick the app profile (REASONS mode)
Decide whether a new app is Profile A (Python backend: storage, auth, multi-user, secrets, schedules, heavy compute) or Profile B (browser-only HTML+JS: a single page the user opens, no backend). Ask the plain-language questions below in the user's language; map the answers to the profile + the spec frontmatter flags.
Profile — ask Q1–Q6 in order; the first YES ⇒ Profile A; all NO ⇒ Profile B
- Q1 Persistent storage — remember data after the app is closed?
- Q2 Authentication — users log in / need to know who did what?
- Q3 Scheduled tasks — run automatically on a schedule?
- Q4 External service needing a secret — connect to a DB/API/service that needs a password/key/token? (B can't hide secrets)
- Q5 Multi-user shared data — several people see/change the same data?
- Q6 Heavy compute / large data — slow or memory-heavy work, or more than a few MB at once?
Flags (always asked; do not change the profile)
- Q7 Personal data →
handles_personal_data(true ⇒ §7.2 GDPR/LOPDGDD mandatory) - Q8 External API →
requires_external_api(true ⇒ every call listed in §5 with an explicit timeout) - Q2 = YES implies
requires_authentication: true.
Profile-B-only flags (N/A in A)
- Q9 Non-personal browser preferences →
uses_localstorage - Q10 Rich UI needing React →
uses_react(suggests Q11 = YES) - Q11 Comfortable with Node.js + npm + build →
uses_npm_build - Q12 Node.js server in production →
runs_node_server(requiresuses_npm_build: true)
Profile-A-only flag (N/A in B)
- Q13 Server-rendered UI vs API-only →
serves_html_ui(A-with-UI vs A-api-only)
UI flag (UI projects only, default YES)
- Q14 Corporate look & feel →
apply_branding(uses a brand skill if you ship one; falls back to neutral)
Tech stack per profile (summary; full rules load on demand)
- A (Python): Python 3.12 · FastAPI · Pydantic v2 · SQLAlchemy 2.x (SQLite dev / PostgreSQL prod) · uv · pytest.
- B (HTML+JS): browser ES modules + CDN/SRI; optional Alpine.js (CSP build), React (+ npm/Vite), or a Node server (Fastify).
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.
- 11d ago First seen · 52 lines · 58 tokens per session scan A 2f9b08b7036d
aiws-sdd-onboarding is a skill published in the GitHub repository grojof/ai-workspace-generator (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session and 755 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…