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/jhostalek/dotclaude/audit-structurenpx skills add JHostalek/dotclaude --skill audit-structuregit clone --depth 1 https://github.com/JHostalek/dotclaudeWrote 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/jhostalek/dotclaude/audit-structure)<a href="https://agentmods.dev/skills/jhostalek/dotclaude/audit-structure"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/audit-structure.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.00077 | $0.02493 |
| Opus 5 | $0.00039 | $0.01247 |
| Sonnet 5 | $0.00015 | $0.00499 |
| Haiku 4.5 | $0.00008 | $0.00249 |
Grade A, and why
audit-structure 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!cat "${CLAUDE_SKILL_DIR}/../shared/audit-workflow.md"
Run as the structure dimension. Find topology and dependency design that makes ownership unclear, couples unrelated change, permits forbidden access, or fails under evolution, deployment, or runtime composition. Do not reduce structure to directory aesthetics.
Work top-down
Reconstruct the system before judging its tree:
- Identify intended behavior, domain and team ownership, deployable/runtime units, trust and data boundaries, public contracts, state and control flows, entry points, extension points, lifecycle paths, and operational modes. Derive structural invariants: what must change together, remain isolated, depend in one direction, or stay replaceable.
- Map those concepts to files, modules, packages, services, build targets, schemas, generated artifacts, infrastructure, tests, and documentation. Build the actual dependency graph, including runtime discovery, dependency injection, generated links, events, queues, shared storage, configuration, deployment coupling, and external consumers—not imports alone.
- Establish intended structure from converging evidence: architecture decisions and policy, enforced boundary configuration, public contracts, ownership, supported framework rules for the exact version, dependency direction, co-change history, release/deployment boundaries, and dominant maintained practice. No source is conclusive alone.
- Inspect architecture-wide boundary failures and dangerous compositions first. Then trace concrete change, build, startup, request, job, event, migration, failure, recovery, and shutdown paths across structural seams.
- Find wide across every applicable baseline area before applying noise filters. Classify each candidate as confirmed defect, worthwhile improvement, intentional constraint, migration state, generated/vendor/framework requirement, or unresolved question.
Do not infer sound structure from a policy file, framework, directory name, clean import graph, barrel, interface, dependency-injection container, helper abstraction, test presence, longstanding layout, or majority convention. Verify the exact consumers, runtime wiring, ownership, lifecycle, and failure behavior. A declared boundary that shared state, events, build coupling, or operational procedures bypass is not an effective boundary.
Repository convention constrains a correction but does not prove the convention correct. Where dominant structure conflicts with behavior, ownership, enforceable boundaries, or a newer explicit architecture, surface the conflict instead of normalizing toward the majority. History and co-change are evidence, not ground truth: repeated joint changes may expose missing cohesion, but can also reflect cross-cutting work, generated output, or an active migration.
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.
- 5d ago First seen · 127 lines · 77 tokens per session scan A 824378f23e54
audit-structure is a skill published in the GitHub repository JHostalek/dotclaude (11 stars, last pushed today), licensed CC0-1.0. It adds 77 tokens to every session and 2,493 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
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
skill-check
Validate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.
agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
skill-template
Generate custom skill/command from template. Use when creating a new skill or slash command from scratch, or scaffolding a skill file with correct frontmatter.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.