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/docxology/template/auditnpx skills add docxology/template --skill auditgit clone --depth 1 https://github.com/docxology/templateWrote 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/docxology/template/audit)<a href="https://agentmods.dev/skills/docxology/template/audit"><img src="https://agentmods.dev/badge/skills/docxology/template/audit.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.1 | $0.00040 | $0.00403 |
| Opus 5 | $0.00020 | $0.00201 |
| Sonnet 5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
template-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 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
template-audit
Audit and quality-gate scripts in scripts/audit/.
When to use
Load this skill when you need to:
- Run documentation or filepath audits
- Check for template drift in exemplar projects
- Enforce confidentiality (no private project commits)
- Verify prohibited mock-framework syntax is absent and inventory semantic stand-ins
Key scripts
| Script | Exit 0 means |
|---|---|
lint_docs.py |
All doc lints pass |
check_tracked_projects.py |
No private projects staged/committed |
check_template_drift.py |
Exemplars are up-to-date |
verify_no_mocks.py |
No prohibited mock-framework imports/calls detected |
Bootstrap note
All scripts use parents[2] from scripts/audit/ — three levels to repo root.
Pitfalls
check_tracked_all.pyruns in pre-push and composes every resource-pool guard; keep each constituent check fast.audit_documentation.pyis advisory; non-zero exit is a warning, not a gate.copy_exemplar.pymodifies tracked files — review diff before committing.verify_no_mocks.py --inventory --max-dependency-replacements 0is blocking in CI. The default lexical pass and the semantic zero-debt gate are distinct contracts; environment isolation remains separately classified.
What ships with it
23 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.
- __init__.py 1.5 KB runs code
- AGENTS.md 4.3 KB
- audit_documentation.py 1.6 KB runs code
- audit_filepaths.py 4.6 KB runs code
- check_backlog.py 933 B runs code
- check_claim_bindings.py 1.5 KB runs code
- check_mirror_symlinks.py 1.7 KB runs code
- check_module_doc_coverage.py 1.9 KB runs code
- check_public_template_contract.py 1.1 KB runs code
- check_staged_secrets.py 1.3 KB runs code
- check_template_drift.py 1.6 KB runs code
- check_tracked_all.py 1.3 KB runs code
- check_tracked_fonds.py 1.1 KB runs code
- check_tracked_generated_artifacts.py 1.9 KB runs code
- check_tracked_projects.py 1.1 KB runs code
- check_tracked_rules.py 1.1 KB runs code
- check_tracked_secrets.py 1.0 KB runs code
- check_tracked_tools.py 1.1 KB runs code
- copy_exemplar.py 360 B runs code
- lint_docs.py 2.3 KB runs code
- README.md 2.4 KB
- test_impact.py 2.8 KB runs code
- verify_no_mocks.py 559 B runs code
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 · 51 lines · 40 tokens per session scan A ae3b2a45e156
template-audit is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 403 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
docs-audit
痛点：代码改了 40 天了，文档还停在 3 个月前。没人专门盯，自然就 drift。这个 skill 每周扫一次、给出有证据的清单，让技术写作不用手动翻 git blame。.
merge-check
Xcode-specific pre-merge gate — archive build (catches strict-concurrency/MainActor errors debug builds miss), app-extension Info.plist check, SwiftLint — spawned in parallel. Trigger on Apple/Xcode merge intent specifically ("merge this iOS branch", "archive check before merge", "is this ready for TestFlight"); a…
skill-scorer
Evaluates Agent Skills (Cursor / Claude / OpenClaw compatible) and produces a quantitative, rubric-based score with actionable improvement suggestions. Use when the user asks to review, rate, audit, grade, lint, or improve a SKILL.md file, a skill folder, or a skill archive, or says things like "给这个 skill 打分", "评估一下…
release
Execute the weekly release checklist for any uFawkes repo. Use when an increment is ready to ship. Implements the write-once-ship-four-times pattern: README → CHANGELOG → GitHub Release → dev.to → LinkedIn → ufawkes.dev.
gitops-overlay
Validate GitOps overlays for correctness and compliance. Use when reviewing kustomize builds, environment overlays, image tags, and secrets.
gitops-sim
Simulate GitOps updates locally without pushing to remote repos. Use when cloning GitOps repo locally, applying OBS updates, or validating manifest correctness.