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 reganomalley/claudia --skill claudia-securitygit clone --depth 1 https://github.com/reganomalley/claudiaWrote 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/reganomalley/claudia/claudia-security)<a href="https://agentmods.dev/skills/reganomalley/claudia/claudia-security"><img src="https://agentmods.dev/badge/skills/reganomalley/claudia/claudia-security/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/reganomalley/claudia/claudia-security"><img src="https://agentmods.dev/badge/skills/reganomalley/claudia/claudia-security.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.00089 | $0.00797 |
| Opus 5 | $0.00044 | $0.00398 |
| Sonnet 5 | $0.00018 | $0.00159 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
claudia-security 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 10d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia Security Domain
Overview
This skill provides security decision frameworks. It doesn't replace a security audit -- it helps you make informed choices and avoid common pitfalls.
Decision Trees
Authentication: Which Method?
What are you building?
├── API consumed by other services
│ ├── Internal only → API keys + mTLS
│ └── External/public → OAuth 2.0 client credentials
├── Web app with users
│ ├── Simple/small scale → Session-based auth (cookie + server session)
│ ├── SPA + API backend → JWT (short-lived) + refresh tokens (httpOnly cookie)
│ └── Enterprise/SSO needs → OIDC with identity provider (Auth0, Okta, Keycloak)
├── Mobile app
│ └── OAuth 2.0 + PKCE (always PKCE for public clients)
└── CLI tool
└── OAuth 2.0 device flow or API key
Secrets: Where Do They Go?
What kind of secret?
├── API keys / tokens
│ ├── Development → .env file (gitignored) + dotenv library
│ ├── CI/CD → Pipeline secrets (GitHub Actions secrets, etc.)
│ └── Production → Secret manager (AWS SSM, Vault, Doppler)
├── Database credentials
│ ├── Local dev → .env or docker-compose env
│ └── Production → Secret manager + IAM roles where possible
├── Encryption keys
│ └── Always → KMS (AWS KMS, GCP KMS, Azure Key Vault)
└── User passwords
└── Never store → bcrypt/argon2 hash only
Common Mistakes (and fixes)
| Mistake | Why It's Bad | Fix |
|---|---|---|
| JWT in localStorage | XSS can steal tokens | httpOnly cookie for refresh, memory for access |
| Long-lived JWT (days/weeks) | Stolen token = long compromise | 15min access + rotating refresh tokens |
| Rolling your own auth | You will miss something | Use a library (Passport, NextAuth, Lucia) |
| Hardcoded secrets in code | Ends up in git history | .env + secret manager |
CORS * in production |
Any site can call your API | Whitelist specific origins |
| No rate limiting on auth | Brute force attacks | Rate limit login + lockout after N failures |
| MD5/SHA1 for passwords | Fast to crack | bcrypt (cost 12+) or argon2id |
| No CSRF protection | Forged requests from other sites | SameSite cookies + CSRF tokens |
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.
- 10d ago First seen · 79 lines · 89 tokens per session scan A ae1eb76bca1f
claudia-security is a skill published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 89 tokens to every session and 797 once invoked, about $0.0004 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…