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 HawkannG/Claude-Warden --skill warden-securitygit clone --depth 1 https://github.com/HawkannG/Claude-WardenWrote 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/hawkanng/claude-warden/warden-security)<a href="https://agentmods.dev/skills/hawkanng/claude-warden/warden-security"><img src="https://agentmods.dev/badge/skills/hawkanng/claude-warden/warden-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/hawkanng/claude-warden/warden-security"><img src="https://agentmods.dev/badge/skills/hawkanng/claude-warden/warden-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.00020 | $0.00761 |
| Opus 5 | $0.00010 | $0.00380 |
| Sonnet 5 | $0.00004 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
warden-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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security & Privacy by Design
Policy Area: Security & Privacy Version: 1.0 Status: Active Enforcement: Advisory (human-approved deviations only) Purpose: Ensure every feature handles data responsibly and follows secure coding defaults
1. Privacy by Design (GDPR Article 25)
All features touching user or personal data MUST follow these principles by default. Deviate only after flagging to the human and getting explicit approval.
| Principle | Rule |
|---|---|
| Data Minimisation | Only collect fields that are strictly necessary |
| Purpose Limitation | Data used only for its stated purpose |
| Storage Limitation | Define retention period; don't keep data forever |
| Accuracy | Provide mechanisms to correct/update personal data |
| Integrity & Confidentiality | Encrypt at rest and in transit where appropriate |
| Accountability | Audit trails for personal data access/changes |
When to Apply
- During PROPOSE/PLAN: Flag any personal data fields in the data model and justify each one. If a field isn't strictly necessary, remove it.
- During BUILD: Default to pseudonymisation where possible. No unnecessary PII. Hash or encrypt sensitive fields.
- During VERIFY: Check that no personal data is logged, leaked in error messages, or exposed in API responses beyond what's needed.
2. Security by Design
These are non-negotiable defaults. Opt-out requires explicit human justification.
Secrets Management
- No hardcoded secrets —
.envonly,.envin.gitignore - Never log secrets, tokens, or credentials
- Never commit secrets — GitGuardian / TruffleHog enforced in CI
- Environment variables for all configuration that varies between environments
Database & Queries
- No raw SQL queries without explicit human approval — use ORM
- Parameterised queries only (no string interpolation in SQL)
- Validate and sanitise all user input before it reaches the database
Authentication & Authorization
- Auth on every endpoint by default — opt-out requires justification
- Password hashing with bcrypt/argon2 (never plain text, never MD5/SHA1)
- Session tokens: secure, httpOnly, sameSite flags
- Role-based access control: principle of least privilege
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 · 90 lines · 20 tokens per session scan A 87f24c0c63bd
warden-security is a skill published in the GitHub repository HawkannG/Claude-Warden (2 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 761 once invoked, about $0.0001 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
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…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
code-mate-antigravity
Runs Antigravity CLI headlessly for repository analysis and coding tasks. Use when the user asks to delegate work to Antigravity CLI or compare its result with another coding agent.