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 raulvidis/openclaw-multi-agent-kit --skill template-auditgit clone --depth 1 https://github.com/raulvidis/openclaw-multi-agent-kitWrote 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/raulvidis/openclaw-multi-agent-kit/template-audit)<a href="https://agentmods.dev/skills/raulvidis/openclaw-multi-agent-kit/template-audit"><img src="https://agentmods.dev/badge/skills/raulvidis/openclaw-multi-agent-kit/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.00054 | $0.01233 |
| Opus 5 | $0.00027 | $0.00616 |
| Sonnet 5 | $0.00011 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
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 7d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install
Copy to agents/<maintainer>/skills/template-audit/SKILL.md for an orchestrator or maintainer agent that owns workspace setup. Run against any directory that mirrors the layout of openclaw-multi-agent-kit/templates/ — a kit checkout, a vendored copy, or an in-progress agent workspace.
Template Audit Skill
Use this when picking which templates to copy into a new workspace, when reviewing a PR that adds or edits templates, or when team prompt size feels heavy and you need to know which SOUL/SKILL files dominate the budget.
When to Use
- Adding a new agent → check the target soul template before copying.
- Adding a new skill → verify frontmatter, install path, and that no near-duplicate exists.
- Workspace bloat → identify the heaviest soul/skill templates by byte size.
- Cross-catalog overlap → confirm whether a core template (e.g.
coding-agent.md) already covers what an extended template offers (e.g.engineering/*).
Audit Checklist
Run these passes against the target directory tree. Report findings; do not edit files in-place unless the user asks.
1. Frontmatter at line 1
For every .md file in templates/soul/**, templates/skills/**/SKILL.md, and templates/identity/*.md:
- The first non-empty line must be
---. - No H1 header, blockquote, or comment above the YAML block.
- Required fields:
- SOUL.md:
name,description(noversionrequired by convention). - SKILL.md:
name,description,version. - IDENTITY.md: free-form; flag only if the file looks templated but missing fields.
- SOUL.md:
Flag any file that fails — these break OpenClaw's loader silently.
2. Duplicate / near-duplicate names
Scan for:
- Same
nameacross core (templates/soul/*.md) and extended (templates/soul/<category>/*.md). - Same
nameacross two extended categories. - Same
nameacrosstemplates/skills/*/SKILL.md.
For each collision report: which file would win, which one should be merged or renamed, and whether bodies overlap >60% (rough word-set similarity is fine — exact diff not required).
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.
- 7d ago First seen · 118 lines · 54 tokens per session scan A 86fca9ec329f
template-audit is a skill published in the GitHub repository raulvidis/openclaw-multi-agent-kit (394 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,233 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…