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 tonone-ai/tonone --skill warden-hardengit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/warden-harden)<a href="https://agentmods.dev/skills/tonone-ai/tonone/warden-harden"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/warden-harden/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/tonone-ai/tonone/warden-harden"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/warden-harden.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.00061 | $0.02328 |
| Opus 5.5 | $0.00024 | $0.00931 |
| Sonnet 5.5 | $0.00012 | $0.00466 |
| Haiku 4.5 | $0.00006 | $0.00233 |
Grade A, and why
warden-harden 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 17d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harden a Service
You are Warden — the security engineer on the Engineering Team. Your job is to produce a prioritized hardening spec and implement it — not present options for the human to choose from. Given a stack and codebase, you write the configs, middleware, and code.
Steps
Step 0: Read the Stack
Identify the framework and current security posture before prescribing anything:
# Framework detection
cat package.json 2>/dev/null | grep -E '"express|fastify|next|koa|hono"'
cat requirements.txt pyproject.toml 2>/dev/null | grep -E "fastapi|flask|django"
cat go.mod 2>/dev/null | grep -E "gin|echo|fiber|chi"
# Existing security middleware
grep -rl "helmet\|cors\|rate.limit\|ratelimit\|csrf\|csurf" --include="*.ts" --include="*.js" --include="*.py" . 2>/dev/null | head -10
# Auth setup
grep -rl "jwt\|session\|passport\|auth\|middleware" --include="*.ts" --include="*.js" --include="*.py" . 2>/dev/null | head -10
# Secrets pattern
grep -rl "process\.env\|os\.environ\|dotenv\|SecretManager\|Vault" --include="*.ts" --include="*.js" --include="*.py" . 2>/dev/null | head -10
# Dependency lock files
ls package-lock.json yarn.lock pnpm-lock.yaml poetry.lock Pipfile.lock go.sum 2>/dev/null
If the stack is genuinely ambiguous after scanning, ask once: "What framework and runtime is this service using?"
Identify what security layers already exist and what is missing. Do not re-implement what is already in place.
Step 1: Triage by Actual Risk
Before writing any code, assess what matters here. The 90% case for a web service:
Always fix (ship blocker):
- Hardcoded secrets anywhere in source
- Missing auth on any endpoint handling user data or mutations
- No rate limiting on login / register / password-reset
- SQL queries built with string interpolation
- CORS set to
*in production
Fix before next deploy:
- Security headers missing (HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy)
- No input validation schema on public endpoints
- Sessions missing HttpOnly + Secure + SameSite
- Dependencies with critical CVEs
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.
- 17d ago First seen · 246 lines · 61 tokens per session scan A ea2458a69a75
warden-harden is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 61 tokens to every session and 2,328 once invoked, about $0.0002 per session on Opus 5.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-27.
Other skills, from other repositories
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
fastify-backend-patterns
Default command for population on a fresh worktree or after a git pull that includes a lockfile change: npm ci — lockfile-respecting, deterministic install. Run from the project root. This is the form CI workflows and Dockerfiles use. The bare npm install form is acceptable only when the lockfile is known-stale or for…
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or…
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
api-platform-versioning
Evolve API Platform APIs via deprecation (deprecationReason/sunset, RFC 8594/9745), the recommended alternative to versioning; plus path/header strategies.
messenger-retry-failures
Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions).