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/davekilleen/dex/messaging-auditnpx skills add davekilleen/Dex --skill messaging-auditgit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/messaging-audit)<a href="https://agentmods.dev/skills/davekilleen/dex/messaging-audit"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/messaging-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.00024 | $0.01098 |
| Opus 5 | $0.00012 | $0.00549 |
| Sonnet 5 | $0.00005 | $0.00220 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
messaging-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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 100 lines · 24 tokens per session scan A ed2685814f2e
messaging-audit is a skill published in the GitHub repository davekilleen/Dex (475 stars, last pushed today), with no licence file. It adds 24 tokens to every session and 1,098 once invoked, about $0.0001 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-02.
Other skills, from other repositories
review-code
Deep code quality review for the inspecto monorepo. Use this skill whenever the user wants to review, audit, or assess the quality of code in the inspecto project — even if they just say "check this file", "is this well written", "review my implementation", or "does this follow the architecture?". Accepts a file path…
vscode-ext-context
Extract raw source code context around a specific VSCode extension command's registerCommand call. Outputs the surrounding N characters of minified code for manual inspection. Use when the user wants to see the actual source code around a command registration, needs to understand the internal implementation details…
vscode-ext-list-commands
List all commands registered by a VSCode extension, including hidden ones not declared in package.json. Given an extension ID (e.g. anthropic.claude-code), finds the installed extension, extracts declared commands from package.json and runtime-registered commands from extension.js. Use when the user asks: what…
inspecto-onboarding-core
Use when creating or maintaining assistant-specific Inspecto onboarding skills that should follow the shared detect, plan, apply, and doctor workflow.
inspecto-onboarding
Help users set up Inspecto in their project or diagnose Inspector runtime issues. Trigger this skill when the user asks "Set up Inspecto in this project" or similar queries.
create-chatccc-feishu-app
Create, clone, or configure a Feishu enterprise self-built bot application for ChatCCC. Use when asked to create a ChatCCC Feishu app, imitate an existing lowercase chatccc app, prepare a bot for another computer, or configure its bot capability, im:/cardkit: permissions, events, credentials, version, and internal…