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/rampstackco/claude-skills/security-baselinenpx skills add rampstackco/claude-skills --skill security-baselinegit clone --depth 1 https://github.com/rampstackco/claude-skillsWrote 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/rampstackco/claude-skills/security-baseline)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/security-baseline"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/security-baseline.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.1 | $0.00103 | $0.02645 |
| Opus 5 | $0.00051 | $0.01323 |
| Sonnet 5 | $0.00021 | $0.00529 |
| Haiku 4.5 | $0.00010 | $0.00265 |
Grade A, and why
security-baseline 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.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Baseline
Establish the security floor for any production website or web app. Stack-agnostic. Covers the things that should be in place before public launch and verified periodically after.
When to use
- Pre-launch security review
- Setting up a new site or environment
- Periodic security audit (quarterly recommended)
- Onboarding a new vendor or third-party integration
- Responding to a security finding or report
- Hardening after an incident
When NOT to use
- Active incident response (use
incident-response) - Code-level security review (use
code-review-web) - Email-specific authentication (SPF/DKIM/DMARC) (use
email-deliverability) - DNS-level security (CAA, DNSSEC) (use
domain-strategy) - Performance-related security (DDoS protection sizing) (use
performance-optimization)
Required inputs
- The site or app in scope (URLs, environments)
- The hosting platform and CDN
- Authentication method (if any)
- Third-party scripts and integrations
- Compliance context (PCI, SOC2, GDPR, etc., if applicable)
- Existing security tooling
The framework: 6 layers
Security is layered. Each layer addresses a different attack surface.
Layer 1: Transport security
How data moves from server to client.
- HTTPS everywhere. No HTTP variants serving content.
- TLS 1.2 minimum, TLS 1.3 preferred. Disable TLS 1.0 and 1.1.
- HSTS (Strict-Transport-Security) header set, with
includeSubDomainsandpreloadfor high-confidence sites. - Strong cipher suites only. Modern browsers handle this if you pick a modern config from your provider.
- Certificates from a trusted CA, monitored for expiration.
Layer 2: Response headers
What the browser is told about your site.
| Header | Purpose | Default value |
|---|---|---|
Strict-Transport-Security |
Force HTTPS | max-age=31536000; includeSubDomains |
Content-Security-Policy |
Restrict resource loading | Site-specific |
X-Content-Type-Options |
Prevent MIME sniffing | nosniff |
X-Frame-Options |
Clickjacking protection | DENY or SAMEORIGIN |
Referrer-Policy |
Control referrer info | strict-origin-when-cross-origin |
Permissions-Policy |
Control browser features | Site-specific (camera, mic, etc.) |
Cross-Origin-Opener-Policy |
Process isolation | same-origin (where compatible) |
Cross-Origin-Embedder-Policy |
Cross-origin restrictions | require-corp (where applicable) |
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.
- 2d ago First seen · 303 lines · 103 tokens per session scan A 9fb2c8030710
security-baseline is a skill published in the GitHub repository rampstackco/claude-skills (817 stars, last pushed 8d ago), licensed MIT. It adds 103 tokens to every session and 2,645 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
recruit-pipeline
Hiring Pipeline Status Report — active roles, candidate counts by stage, time-in-stage analysis, bottleneck identification, recommended next actions.
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
golden-rss
Use when testing the rss golden build.