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 shopwareLabs/ai-coding-tools --skill structuring-documentationgit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/structuring-documentation)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/structuring-documentation"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/structuring-documentation/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/shopwarelabs/ai-coding-tools/structuring-documentation"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/structuring-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.02627 |
| Opus 5.5 | $0.00036 | $0.01051 |
| Sonnet 5.5 | $0.00018 | $0.00525 |
| Haiku 4.5 | $0.00009 | $0.00263 |
Grade A, and why
structuring-documentation 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 1mo 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structuring Documentation
Treat every Markdown file in scope as a documentation surface. Each one holds one subject, one content class, and a bounded amount of reading.
The surfaces in scope are the paths the user names, or the documentation files the current change touches. The script has no default scope and requires explicit paths. When no scope is stated, ask for it rather than assuming one.
Nothing here gates a build. The measurement reports; you act on what it reports.
Budgets are named values: docs.size_goal (default if not otherwise stated: 5000), docs.size_limit (6500), docs.size_ceiling (10000), docs.max_index_rows (20). When earlier context or a user instruction assigns a different value, pass it to the script as --goal, --limit, --ceiling, or --max-index-rows; otherwise run the script on its built-in defaults. When earlier context supplies a subject-ownership table for the project, use it wherever the workflow consults ownership.
Workflow
digraph doc_surfaces {
node [shape=box];
start [shape=doublecircle, label="editing or auditing\na doc surface"];
scope [label="determine the surfaces in scope\n(ask when none is stated)"];
measure [label="run measure.sh size + links"];
subjects [shape=diamond, label="each surface holds one subject,\nowned by its directory\n(references/surface-contract.md)?"];
rehome [label="split the surface, or move the\nsubject to its owning directory"];
over [shape=diamond, label="verdict over\n(above docs.size_ceiling, 10000)?"];
limit [shape=diamond, label="verdict allowance\n(above docs.size_limit, 6500)?"];
crit [shape=diamond, label="is a criterion\ntrue of this file?"];
goal [shape=diamond, label="verdict allowed\n(above docs.size_goal, 5000) with an\nobvious section boundary?"];
split [label="split into docs/ siblings\n(references/splitting.md)"];
nocrit [label="no criterion holds: length alone\nis not one, and neither is\npreferring not to split — split"];
mark [label="mark the allowance or exemption\nunder the title (for size-exempt,\nverify the parsing consumer first)"];
rows [shape=diamond, label="routing rows above\ndocs.max_index_rows (20)?"];
group [label="introduce an\nintermediate grouping"];
links [label="repair citations: convert bare paths,\nfix dead targets and stale anchors,\nrelink restating anchors"];
moved [shape=diamond, label="did this change create a directory\nor move a section body?"];
sweep [label="run the three sweeps, then run\nthem again after the repairs"];
recheck [label="re-run measure.sh"];
resolved [shape=diamond, label="every finding repaired, or\ndismissed with a stated reason?"];
done [shape=doublecircle, label="findings resolved\nor dismissed"];
start -> scope -> measure -> subjects;
subjects -> rehome [label=" no"];
rehome -> over;
subjects -> over [label=" yes"];
over -> split [label=" yes"];
over -> limit [label=" no"];
limit -> crit [label=" yes"];
limit -> goal [label=" no"];
crit -> mark [label=" yes"];
crit -> nocrit [label=" no"];
nocrit -> split;
goal -> split [label=" yes"];
goal -> rows [label=" no"];
split -> rows;
mark -> rows;
rows -> group [label=" yes"];
group -> links;
rows -> links [label=" no"];
links -> moved;
moved -> sweep [label=" yes"];
moved -> recheck [label=" no"];
sweep -> recheck;
recheck -> resolved;
resolved -> over [label=" no"];
resolved -> done [label=" yes"];
}
What ships with it
4 files 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.
- 1mo ago First seen · 182 lines · 89 tokens per session scan A 70cc6c9f979c
structuring-documentation is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 2,627 once invoked, about $0.0004 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-30.
Other skills, from other repositories
release
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and publish to npm through the release workflow. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
doc-html-slide
A renderer that turns presentation content into a single HTML slide deck that opens directly in a browser. It creates a 16:9 slide sequence with navigation, fullscreen viewing, printing to PDF, and speaker-note controls.
setup-mcp-connector
A step-by-step setup guide for connecting Cowork to services such as Google Drive, Notion, and Higgsfield, plus Korean public-data, document, statistics, architecture, and law services. It explains authentication, API keys, test calls, and troubleshooting.
media-gpt-image-prompt
An image-prompt writing tool that turns a natural-language idea into detailed prompts for GPT Image 2.5. It can also adapt the same idea for Gemini 3 Pro Image and Midjourney.
career-portfolio
A portfolio-building skill for Korean job seekers that organizes projects and explains their work for development, design, marketing, and planning roles.
ai-slop-reviewer
A writing review step that detects formulaic patterns often found in AI-generated text and rewrites the wording to sound more natural and human.