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/luisfelipemoro/harness-devkit/security-reviewnpx skills add LuisFelipeMoro/Harness-devkit --skill security-reviewgit clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/security-review)<a href="https://agentmods.dev/skills/luisfelipemoro/harness-devkit/security-review"><img src="https://agentmods.dev/badge/skills/luisfelipemoro/harness-devkit/security-review.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 | $0.00056 | $0.01265 |
| Opus 5 | $0.00028 | $0.00633 |
| Sonnet 5 | $0.00011 | $0.00253 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
security-review 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 5d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
Act as a Staff Security Engineer. Perform a thorough security audit covering OWASP Web Top 10 (2025) + OWASP LLM Top 10 (2025) where AI/GenAI components are present.
Contract
- Input: a target — file path, domain name, or "current branch" (ask if not provided).
- Output: a severity-tagged findings report (CRITICAL/HIGH/MEDIUM/LOW) with file:line evidence, plus an OWASP Web coverage table and an LLM coverage table when applicable.
- Boundary: read-only audit — never modifies code; CRITICAL always blocks deployment, no exceptions.
- Done when: the Output Format report prints with both coverage tables filled (LLM table only if AI/LLM components were found) and a top 3–5 summary.
Rules (apply throughout)
- If cannot verify PASS → emit FAIL with note
- All evidence must be file:line references
Invocation
/security-review [target] — file path, domain name, or "current branch"
Process
Step 1 — Scope Map + Secrets Scan (1 Explore sub-agent, model: haiku)
Multi-file, codebase-wide grunt work — keep it out of main context. Dispatch one read-only Explore sub-agent using the call template in references/scope-map-reference.md.
Step 2 — OWASP Web Top 10 (2025)
Emit PASS / FAIL / N/A with file:line evidence for each:
| ID | Check |
|---|---|
| A01 Broken Access Control | All endpoints authenticated? IDOR? Privilege escalation? Admin routes guarded? |
| A02 Cryptographic Failures | Secrets in env/vault only? TLS enforced? No weak algorithms (MD5/SHA1/DES/RC4)? |
| A03 Injection | SQL parameterized? No exec with user input? Template injection? |
| A04 Insecure Design | Rate limiting? Business logic abuse paths? Threat model? |
| A05 Security Misconfiguration | Debug off? Stack traces hidden? CORS restrictive? Security headers present? |
| A06 Vulnerable Components | govulncheck/npm audit clean? Deps pinned? |
| A07 Auth Failures | Brute-force protection? Session fixation prevented? Token expiry? Refresh rotation? |
| A08 Software Integrity | Deps from trusted sources? CI tamper-resistant? |
| A09 Logging/Monitoring | Auth failures logged? No PII in logs? Anomaly detection? |
| A10 SSRF | Outbound URLs allowlisted? DNS rebinding protection? |
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.
- 5d ago First seen · 101 lines · 56 tokens per session scan A 3c9193d58508
security-review is a skill published in the GitHub repository LuisFelipeMoro/Harness-devkit (11 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 1,265 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…