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/robconery/kolea/security-webnpx skills add robconery/kolea --skill security-webgit clone --depth 1 https://github.com/robconery/koleaWhat 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.00207 | $0.03019 |
| Opus 5 | $0.00103 | $0.01510 |
| Sonnet 5 | $0.00041 | $0.00604 |
| Haiku 4.5 | $0.00021 | $0.00302 |
Grade A, and why
security-web 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 2d 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.
This is a copy
100% identical to security-web — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Application Security Review
Treat every byte that crossed a network boundary as hostile until proven
otherwise, and prove it on the server. The client is an untrusted rendering
surface you do not control. Frameworks add convenience (Server Actions,
Nitro routes, Bun.serve, Hono middleware) that hides the trust boundary
— this skill's job is to make the reviewer see the boundary the framework
obscured.
🎯 Why: Design for Change
The goal of writing software is to be able to change it safely. Secure-by-default config (CSP, cookie flags, parameterized queries, authz-at-the-edge) means the next feature ships without re-litigating the threat model. Every insecure default you accept becomes a foothold the next change has to step around.
This skill is for security review and secure implementation. For general
TypeScript correctness use typescript-best-practices; for schema-level
integrity use postgres-dba. This skill never assumes another layer will
catch it.
How to use this skill (review workflow)
- Map the attack surface first. Identify every trust boundary: HTTP
handlers, Server Actions, form posts, websocket frames, file uploads,
outbound fetches,
postMessage,process.envreaching the client, third-party script tags. A vuln you didn't enumerate is a vuln you didn't find. - Triage each input against the decision guide below; open the matching
references/*.mdfor the exploit, the vulnerable pattern, the fix, and the false-positive caveat. - Apply the framework reference (
references/nextjs.md,nuxt.md,bun.md,hono.md) — the generic finding almost always has a framework-specific trap or a framework-specific fix. - Report findings in the standard format (
templates/finding.md): severity, location (file:line), a concrete exploit walkthrough, and the minimal fix. No exploit path stated → it is an observation, not a finding; say which. - Recommend the secure default, not a bespoke patch. The
templates/configs (CSP, security headers, cookies, CORS) are the target state; a one-off escape is a stopgap.
What ships with it
11 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.
- references/backend.md 13 KB
- references/bun.md 4.1 KB
- references/frontend.md 8.9 KB
- references/hono.md 4.4 KB
- references/nextjs.md 4.2 KB
- references/nuxt.md 3.6 KB
- templates/cors.md 1.8 KB
- templates/finding.md 1.9 KB
- templates/input-validation.ts 2.1 KB runs code
- templates/review-checklist.md 2.4 KB
- templates/security-headers.md 3.4 KB
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.
- 2d ago First seen · 208 lines · 207 tokens per session scan A e9026350da7e
security-web is a skill published in the GitHub repository robconery/kolea (1 stars, last pushed 2d ago), licensed MIT. It adds 207 tokens to every session and 3,019 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-web, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
supermemory
Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for…
moemail
Use when an AI agent needs a temporary/disposable email address — for receiving verification emails, testing email integrations, or any task requiring a temporary inbox via the moemail CLI.
moemail
Use when working in this repository and an AI agent needs a temporary/disposable email address through the MoeMail CLI.
create-saasmail-template
Write, validate, and create email templates for a saasmail instance — the full {{variable}} interpolation grammar, conditional/repeating {{#section}} rendering, HTML escaping, and the required-vs-optional send contract. Use this skill whenever the user is authoring or editing a saasmail email template, or asks…
saasmail-onboarding
Interactive setup wizard for deploying your own saasmail instance to Cloudflare. Use this skill when the user wants to set up saasmail, deploy it, configure Cloudflare resources, or get started with the project. Also trigger when the user says "onboarding", "setup", "deploy saasmail", "get started", or asks how to…
use-saasmail
Send transactional emails and enroll recipients in drip sequences through a deployed saasmail instance's HTTP API. Use this skill whenever the user wants to programmatically send mail, fire off a template, kick off an onboarding/drip sequence, manage recipient enrollment, or integrate their app with their self-hosted…