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 minghinmatthewlam/agent-guards --skill explain-reportgit clone --depth 1 https://github.com/minghinmatthewlam/agent-guardsWrote 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/minghinmatthewlam/agent-guards/explain-report)<a href="https://agentmods.dev/skills/minghinmatthewlam/agent-guards/explain-report"><img src="https://agentmods.dev/badge/skills/minghinmatthewlam/agent-guards/explain-report/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/minghinmatthewlam/agent-guards/explain-report"><img src="https://agentmods.dev/badge/skills/minghinmatthewlam/agent-guards/explain-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00069 | $0.00435 |
| Opus 5.5 | $0.00028 | $0.00174 |
| Sonnet 5.5 | $0.00014 | $0.00087 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
explain-report 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 1mo 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
Explain Report
Create a focused HTML artifact that helps the user understand and retain important project knowledge. Default to concise chat when an artifact would not add meaningful value.
Apply concisely's teaching guidance throughout the artifact.
Content
- Lead with the essential mental model, result, or decision.
- Focus on what helps the user understand the project and decide what to do next.
- Support claims with source files, tests, screenshots, logs, citations, or other material evidence.
- Separate verified facts from inference, uncertainty, and open questions.
- Put supporting depth after the main explanation or behind
<details>. - Adapt the structure and depth to the subject. Do not force fixed modes, sections, or finding counts.
Use a visual only when it makes an important relationship easier to understand. Choose the simplest useful form, such as a flow, comparison, timeline, hierarchy, or before-and-after view.
Artifact
Write one self-contained .html file with embedded CSS. Keep it readable without JavaScript, responsive, accessible, and concise at the top.
Store retained reports at:
~/.codex/artifacts/reports/YYYY-MM-DD-<slug>.html
Use /tmp for disposable or exploratory reports. Keep reports outside the repository unless the user asks otherwise.
Before closing, confirm the file exists, opens as HTML, and represents important evidence accurately. Then use concisely for the chat response: state the result, link the report, and mention any decision or residual uncertainty without repeating the report.
Avoid
- Do not use presentation as a substitute for investigation or verification.
- Do not create decorative dashboards or visuals that repeat the prose.
- Do not bury information that changes what the user should believe or do.
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.
- 1mo ago Changed · +2 lines 7dd2cd47c25c
- 1mo ago First seen · 40 lines · 69 tokens per session scan A f9ae148a08be
explain-report is a skill published in the GitHub repository minghinmatthewlam/agent-guards (47 stars, last pushed 8d ago), licensed MIT. It adds 69 tokens to every session and 435 once invoked, about $0.0003 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…