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 MichaelYcJo/SpecSeal --skill security-auditgit clone --depth 1 https://github.com/MichaelYcJo/SpecSealWrote 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/michaelycjo/specseal/security-audit)<a href="https://agentmods.dev/skills/michaelycjo/specseal/security-audit"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/security-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.00057 | $0.00650 |
| Opus 5 | $0.00028 | $0.00325 |
| Sonnet 5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
security-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 6d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specseal:security-audit — a checklist walked the same way every time
A scan finds what it was built to look for. The value of a written checklist
is the opposite property: it covers the same ground on a bad day as on a good
one. Walk every heading and say none found explicitly — a silently skipped
section reads exactly like a clean one.
What this checklist assumes. It describes a service that takes untrusted input over a network: injection through request data, sessions and authorization, data at rest and in transit, deployment configuration. That is the shape of most OWASP material and it is the shape of this file.
Other projects have real threats this will not name. A mobile or desktop client worries about local storage, keychain use, certificate pinning, and what a rooted device can read. An embedded target worries about firmware signing and physical access. A library worries about what it does with attacker-controlled input on behalf of its callers, and about its own supply chain. A data pipeline worries about what leaks into logs and derived datasets.
Say which of those the project is before walking the list. If the answer is "none of the above", a clean report here means the checklist did not apply — say that instead of reporting a pass.
OWASP Top 10 Check
Injection
- SQL: parameterized queries used?
- XSS: output encoding applied?
- Command: user input in shell commands?
- Path traversal: file paths validated?
Authentication & Authorization
- Passwords properly hashed (bcrypt/argon2)?
- Session management secure?
- Auth checks on every endpoint?
- RBAC/ABAC properly implemented?
Data Protection
- Sensitive data encrypted at rest?
- TLS for data in transit?
- PII handling compliant?
- No secrets in code/logs/errors?
Configuration
- Debug mode off in production?
- CORS properly configured?
- Security headers present?
- Dependencies up to date?
Input Validation
- All user input validated at boundary
- Whitelist over blacklist
- File upload restrictions
- Rate limiting on sensitive endpoints
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.
- 6d ago First seen · 86 lines · 57 tokens per session scan A e0538336f8d3
security-audit is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 650 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-31.
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…