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 hamzaPixl/pixl-ai --skill security-scangit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/security-scan)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/security-scan"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/security-scan/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/hamzapixl/pixl-ai/security-scan"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/security-scan.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.01385 |
| Opus 5.5 | $0.00020 | $0.00554 |
| Sonnet 5.5 | $0.00010 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
security-scan 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Read config.json in this skill directory (if it exists):
scan_scope— default scope when none given; default "full"severity_threshold— minimum severity to report; default "MEDIUM"skip_modules— directories to exclude; default ["node_modules", ".next", "dist", "pycache"]
If invoked without arguments, use scan_scope as the default. Override with the argument if provided.
Security Scan
Automated security scanning across multiple dimensions.
Required References
Before starting, read references/standards/security-audit.md for OWASP patterns and severity classification.
Step 0: Parse Scope
| Scope | What it checks |
|---|---|
secrets |
Hardcoded API keys, passwords, private keys |
owasp |
OWASP Top 10 vulnerability patterns |
deps |
Dependency CVEs via npm audit / pip audit |
rbac |
Authorization checks on routes and endpoints |
full |
All of the above |
Default scope: full. Optional path restricts scanning to a subdirectory.
Step 1: Secrets Scan
Search for common secret patterns:
# API keys
grep -rn 'sk_live_\|sk_test_\|AKIA[A-Z0-9]\|ghp_\|gho_\|xox[bpas]-' --include='*.ts' --include='*.js' --include='*.py' --include='*.go' .
# Private keys
grep -rn 'BEGIN.*PRIVATE KEY' .
# Hardcoded passwords
grep -rn 'password\s*=\s*["\x27][^"\x27]*["\x27]' --include='*.ts' --include='*.js' --include='*.py' .
# .env files committed
git ls-files | grep -E '\.env($|\.local|\.prod|\.staging)'
Severity: CRITICAL for any finding.
Step 2: OWASP Top 10
Scan for common vulnerability patterns:
| OWASP | Pattern to grep |
|---|---|
| SQL Injection | String concatenation in SQL queries |
| XSS | dangerouslySetInnerHTML, unescaped template vars |
| SSRF | User-controlled URLs in fetch/axios calls |
| Broken Auth | Missing auth middleware on routes |
| Insecure CORS | origin: '*' or credentials: true with wildcard |
| Path Traversal | ../ in file operations with user input |
| Hardcoded JWT | JWT secrets as string literals |
What ships with it
3 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.
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 First seen · 149 lines · 51 tokens per session scan A ef6ea1aed713
security-scan is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,385 once invoked, about $0.0002 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-09-03.
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…