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 marcoguillermaz/Tierward --skill doc-auditgit clone --depth 1 https://github.com/marcoguillermaz/TierwardWrote 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/marcoguillermaz/tierward/doc-audit)<a href="https://agentmods.dev/skills/marcoguillermaz/tierward/doc-audit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/doc-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/marcoguillermaz/tierward/doc-audit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/doc-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.00048 | $0.03939 |
| Opus 5 | $0.00024 | $0.01969 |
| Sonnet 5 | $0.00010 | $0.00788 |
| Haiku 4.5 | $0.00005 | $0.00394 |
Grade A, and why
doc-audit scanned grade A with 1 finding 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 10d 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.
Enumerates other installed skillslowAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills/ | grep -v '^custom-' | wc -l Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope for v1
- Static analysis only. Grep, file parsing, filesystem reads. Does not fetch URLs, does not run builds, does not execute code examples.
- No auto-fix. Produces a markdown report; corrections are proposed but never applied.
- Live link check deferred. HTTP/HTTPS targets are out of scope (flaky, rate-limited). Tracked as
DOC-live-links. - Semantic drift deferred. Prose obsolescence, deprecation-age reasoning, and doc-bloat judgement are judgment-heavy and out of scope for v1.
Configuration (adapt before first run)
Replace these placeholders:
[DOC_PATH]- primary location of user-facing docs (e.g.docs/,documentation/,website/). Always included.[README_PATH]- repository README (usuallyREADME.mdat project root).[ADR_PATH]- ADR directory if present (e.g.docs/adr/,docs/decisions/). Leave empty if none.
Step 0 - Target resolution
Parse $ARGUMENTS for a target: or mode: token.
| Pattern | Meaning |
|---|---|
target:path:<dir> |
Audit docs under a specific directory only (e.g. target:path:docs/api) |
target:file:<glob> |
Audit files matching the glob (e.g. target:file:docs/**/*.md) |
mode:all / no argument |
Full audit - README, CHANGELOG, every .md under [DOC_PATH], and ADRs under [ADR_PATH] if set. |
STRICT PARSING: derive target ONLY from explicit text in $ARGUMENTS. Do NOT infer from conversation context, recent blocks, or memory.
Announce: Running doc-audit - scope: [FULL | target: <resolved>] - stack: <pending detection>
Step 1 - Stack detection
Detect the primary stack in this priority order. First matching marker wins.
| Stack | Marker file(s) |
|---|---|
| node-ts | tsconfig.json + package.json |
| node-js | package.json (no tsconfig.json) |
| python | pyproject.toml or requirements.txt or setup.py |
| go | go.mod |
| rust | Cargo.toml |
| swift | Package.swift or *.xcodeproj / *.xcworkspace |
| kotlin | build.gradle.kts or build.gradle with kotlin( plugin |
| dotnet | *.csproj or *.sln |
| ruby | Gemfile |
| java | pom.xml or build.gradle (no Kotlin plugin) |
| generic | None of the above |
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.
- 10d ago First seen · 272 lines · 48 tokens per session scan A f2b44cc5b0ec
doc-audit is a skill published in the GitHub repository marcoguillermaz/Tierward (4 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 3,939 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
harness-engineering
Use when the user asks to improve, fix, or build their repository's AI harness — AGENTS.md, rules, skills, commands, hooks, guardrails, CI sensors — or to act on harness-score audit findings and raise their maturity level.
codex-hud
Show Codex workspace context with local config, git state, hooks, and project hints. Standalone mode can show an expanded snapshot; patched Codex TUI footer mode is single-line. Use when the user says "codex-hud", "show Codex HUD", "status HUD", "workspace snapshot", or asks for richer Codex context.
address-conductor-comment
A workflow for handling pending Conductor code-review comments, including reading their discussion and assigning changes to subagents when appropriate.
explain-comment
A skill that reads a specified file or code range and adds explanatory comments in Japanese. The comments use a question style and focus on important logic, design choices, and side effects.
saleae-mcp-debugger
Use this skill for hardware-in-the-loop firmware capture and decode workflows through the Saleae Logic 2 MCP server.
build-feature
Full pipeline: evaluation -> spec -> implementation -> review -> QA.