Borrowing it
Nothing to install: this file belongs to grojof/ai-workspace-generator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/grojof/ai-workspace-generator/main/.claude/skills/aiws-audit/SKILL.mdgit 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-audit)<a href="https://agentmods.dev/skills/grojof/ai-workspace-generator/aiws-audit"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-audit/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-audit"><img src="https://agentmods.dev/badge/skills/grojof/ai-workspace-generator/aiws-audit.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.00056 | $0.00515 |
| Opus 5 | $0.00028 | $0.00258 |
| Sonnet 5 | $0.00011 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
aiws-audit 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-audit
Produce a periodic, read-only self-audit of this workspace and write it as a dated report, so the project improves from its own state over time. It reports and recommends — it never fixes.
How to work
- Gather signals (all read-only):
ai-workspace doctor— token budget, orphaned blocks, dangling doc references, orphan docs, stack/MCP registry.ai-workspace verify— integrity of base artifacts vs the manifest (tampering / in-region drift).ai-workspace reconcile— company overlay vs base (only if a company overlay is configured).- Repo health —
git status/log, the test/lint/build scripts, and the declareddocs.contract.
- Synthesize findings into severity tiers — 🔴 must-fix · 🟡 should · 🟢 watch — each with what, why it matters, and a concrete recommendation. Prioritize coherence gaps (the harness preaching standards the repo doesn't meet) and drift, since those are what silently rot.
- Write the report to
docs/development/audits/<YYYY-MM-DD>-audit.md(dated, so improvements compound across audits). Link the previous report so progress is visible. - Present the top findings and propose next steps. Make no changes here — fixes go through the normal
flow (SDD for non-trivial,
doctor/syncfor coherence) with the user's approval.
Quality bar
- Every finding is evidence-backed (a command output or a
file:line), not a guess - Findings are prioritized; the report leads with what matters most
- Read-only: nothing is edited — recommendations only
- The report is dated and self-contained (a reader needs no extra context)
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 · 35 lines · 56 tokens per session scan A adfa7415efaa
aiws-audit is a skill published in the GitHub repository grojof/ai-workspace-generator (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 56 tokens to every session and 515 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…
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…