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 agentmods add skills/sunholo-data/ailang-parse/audit-design-docsnpx skills add sunholo-data/ailang-parse --skill audit-design-docsgit clone --depth 1 https://github.com/sunholo-data/ailang-parseWrote 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/sunholo-data/ailang-parse/audit-design-docs)<a href="https://agentmods.dev/skills/sunholo-data/ailang-parse/audit-design-docs"><img src="https://agentmods.dev/badge/skills/sunholo-data/ailang-parse/audit-design-docs.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.00468 |
| Opus 5 | $0.00039 | $0.00234 |
| Sonnet 5 | $0.00016 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
audit-design-docs 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 3d 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
Audit Design Docs
How It Works
The audit compares the project's current version (from ailang.toml) against every design doc in design_docs/ and flags inconsistencies. The implemented/ folder is a changelog — version folders reflect the actual release each feature shipped in. The planned/ folder has target versions for future work.
Workflow
Step 1: Get Current Version
grep '^version' ailang.toml
Step 2: Run the Audit Script
bash .claude/skills/audit-design-docs/scripts/audit.sh
Step 3: Review Findings
| Category | Severity | Meaning |
|---|---|---|
VERSION_MISMATCH |
High | Implemented doc with version > current (impossible — hasn't shipped) |
STATUS_CONTRADICTION |
High | Doc's Status: header contradicts its folder |
LOOSE_FILE |
Medium | File not in a version subfolder |
STALE_PLANNED |
Medium | Planned doc with version <= current (should be implemented or re-versioned) |
Step 4: Propose and Execute Fixes
For each finding, propose a move. Use git mv for tracked files. Always ask user to confirm before executing. After moves, update design_docs/README.md.
Rules
- Never delete design docs — move to
archive/if superseded implemented/folders must use the actual release version, not the design milestone version- The Go binary doc is intentionally unversioned (blocked on external compiler bugs) — don't flag it
- When moving to
implemented/, strip old version prefixes from filenames - Update Status: headers when moving docs between folders
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.
- 3d ago First seen · 46 lines · 79 tokens per session scan A 8902ad1c3604
audit-design-docs is a skill published in the GitHub repository sunholo-data/ailang-parse (0 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 468 once invoked, about $0.0004 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
document-converter
Convert Office documents (PPTX, DOCX, XLSX, PDF, HTML, CSV, JSON, XML, images) to Markdown using Microsoft MarkItDown. Provides the agent with conversion strategies for academic and research workflows.
office-router
Route Office requests into the correct xlsx, docx, or pptx workflow, while preferring Slidev for new presentation drafts unless .pptx is explicitly required.
doc-converter
Universal document format converter - DOCX, PDF, Markdown, HTML, TXT.
document-processing
End-to-end document processing agent skill covering PDF manipulation (extract, merge, split, rotate, watermark, form-fill, OCR), DOCX creation and editing (templates, mail-merge, style management), XLSX spreadsheet handling (formulas, charts, pivot tables, data analysis), PPTX presentation generation (layouts, charts…
anywrite
Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed.
docx-architecture-audit
Audit the office-open-xml-viewer DOCX layout architecture for a single immutable layout-to-paint pipeline. Use after major DOCX layout, pagination, measurement, paint, parser-model, worker, or compatibility changes, and before declaring Issue.