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-reviewgit 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-review)<a href="https://agentmods.dev/skills/grojof/ai-workspace-generator/aiws-sdd-spec-review"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-spec-review/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-review"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-sdd-spec-review.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.00049 | $0.00689 |
| Opus 5.5 | $0.00020 | $0.00276 |
| Sonnet 5.5 | $0.00010 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
aiws-sdd-spec-review 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 2mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aiws-sdd-spec-review — revise a spec & drive the status lifecycle (REASONS mode)
The maintenance counterpart of aiws-sdd-spec-capture: every change to a saved spec, plus the status
transitions. Always show a git diff and ask before saving. Versioning is Git (history + PRs) — the
frontmatter.version + §0 Changelog stay as an informative trail; there are no _vN filenames or manual archive/.
Locate & validate
Pick the active spec in {{paths.specs}}/ (by spec_id; ask if several). Verify the frontmatter parses, the 8
H1 sections are present, and status is one of the five values. A corrupted spec is fixed first, never edited blindly.
Edits
Classify: content edit · structural add (reuse aiws-sdd-spec-capture's per-section questions) · removal
(cascade-check §2↔§5 references) · flag toggle (include/exclude §3.3 auth, §3.4 storage, §7.2 PD) · profile
promotion B→A (structural rewrite, re-run aiws-sdd-onboarding). Re-validate against aiws-sdd-spec-schema before
saving. Show the diff; on confirm, commit (a content change after user-reviewed bumps version + a §0 bullet).
Status lifecycle (sign-off gates)
draft → user-reviewed → it-approved → implemented → retired (linear; reopen/fail steps back one).
| From → To | Gate | Effect |
|---|---|---|
| draft → user-reviewed | full aiws-sdd-spec-schema checklist green; reviewers non-empty; UI specs: mockup accepted |
§0 sign-off bullet (Reviewer: <email>); no version bump |
| user-reviewed → draft | user reopens | bump version; §0 "reopened" |
| user-reviewed → it-approved | all four sdd-audit-* green (recorded) |
§0 IT signature; status-only |
| it-approved → user-reviewed | any audit failure | §0 failure reason |
| it-approved → implemented | deployment (out of scope) | §0 deploy date |
| implemented → retired | explicit decision | §0 retire note |
Refuse any transition not in the table (e.g. draft → it-approved directly). Code/tests are generated only
from user-reviewed or later. Record each transition in {{paths.changes}}/<change>/. Spec keys/headings stay
English; only the conversation follows config.language.
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.
- 2mo ago First seen · 45 lines · 49 tokens per session scan A 653023993338
aiws-sdd-spec-review is a skill published in the GitHub repository grojof/ai-workspace-generator (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 689 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…