cassini-workshop: Skill for Claude Code

.claude/skills/security-web/SKILL.md

security-web is a skill for Claude Code from opagani/cassini-workshop. It costs 207 tokens per session (3,019 once invoked), scanned A, a copy of security-web, MIT.

A review guide for securing TypeScript and JavaScript web applications. It covers risks such as cross-site scripting, request forgery, leaked secrets, broken access control, injection, unsafe file handling, and server-side request forgery.

In plain words
What is it for?
Use it to review or securely implement frontend and backend web features, including HTTP handlers, forms, server actions, file uploads, outbound requests, authentication, and authorization.
Why use it?
It helps find weaknesses at the boundary between untrusted network input and application behavior, including security issues that frameworks can hide.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is opagani/cassini-workshop's own configuration. It tells Claude Code how to work on cassini-workshop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cassini-workshop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to opagani/cassini-workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/opagani/cassini-workshop/main/.claude/skills/security-web/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/opagani/cassini-workshop

Made for: Claude Code.

Wrote 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.

agentmods badge for security-web

README.md
[![agentmods](https://agentmods.dev/badge/skills/opagani/cassini-workshop/security-web/github.svg)](https://agentmods.dev/skills/opagani/cassini-workshop/security-web)
Your own site
<a href="https://agentmods.dev/skills/opagani/cassini-workshop/security-web"><img src="https://agentmods.dev/badge/skills/opagani/cassini-workshop/security-web/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.

agentmods 80×15 button for security-web

Your own site · 80×15
<a href="https://agentmods.dev/skills/opagani/cassini-workshop/security-web"><img src="https://agentmods.dev/badge/skills/opagani/cassini-workshop/security-web.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 207 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,019 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00207 $0.03019
Opus 5.5 $0.00083 $0.01208
Sonnet 5.5 $0.00041 $0.00604
Haiku 4.5 $0.00021 $0.00302

Measured 2mo ago against content hash e9026350da7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (templates/input-validation.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

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.

.claude/skills/security-web/SKILL.md · 208 lines

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)

  1. Map the attack surface first. Identify every trust boundary: HTTP handlers, Server Actions, form posts, websocket frames, file uploads, outbound fetches, postMessage, process.env reaching the client, third-party script tags. A vuln you didn't enumerate is a vuln you didn't find.
  2. Triage each input against the decision guide below; open the matching references/*.md for the exploit, the vulnerable pattern, the fix, and the false-positive caveat.
  3. 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.
  4. 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.
  5. 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.

Read the full file on GitHub · 208 lines

Changes

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.

  1. 2mo ago First seen · 208 lines · 207 tokens per session scan A e9026350da7e

Subscribe to this mod's changes

security-web is a skill published in the GitHub repository opagani/cassini-workshop (0 stars, last pushed 4mo ago), licensed MIT. It adds 207 tokens to every session and 3,019 once invoked, about $0.0008 per session on Opus 5.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.

Related

Other skills, from other repositories

add-provider

Add a new storage or service provider to the core package. Use when implementing a new backend for StorageService (e.g., a new database) or a new service provider (e.g., a new LLM backend).

cyanheads/mcp-ts-core · 47 tokens

add-export

Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).

cyanheads/mcp-ts-core · 50 tokens

flaremo-memory

A shared memory ledger for coding agents. It defines how agents check project rules, record facts during work, and save a handoff report at the end.

realchendahuang/FlareMo · 138 tokens

context

Use whenever the user asks about their own work, projects, decisions, people, preferences or past sessions, and before ending any session that produced something worth keeping. The user's Context is their own notes, reached through the context MCP server; this skill says when to read it and how to write back.

Supa-Media/context · 64 tokens

how-we-define-chaos

How Context scores a workspace's chaos, and how to organize notes so it goes down. Use when the user asks you to tidy, organize, clean up or restructure their notes or folders, asks about their chaos score, or when a write or move answer reports the score got messier.

Supa-Media/context · 65 tokens

sync

Copy what you already know about the user into their Context, adding to what other AI apps wrote before. Run when the user asks to set up, fill in, import into, or sync their Context, or right after connecting a new AI app.

Supa-Media/context · 52 tokens