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 rana/skills --skill hardening-auditgit clone --depth 1 https://github.com/rana/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/rana/skills/hardening-audit)<a href="https://agentmods.dev/skills/rana/skills/hardening-audit"><img src="https://agentmods.dev/badge/skills/rana/skills/hardening-audit/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/rana/skills/hardening-audit"><img src="https://agentmods.dev/badge/skills/rana/skills/hardening-audit.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.00063 | $0.01099 |
| Opus 5 | $0.00032 | $0.00549 |
| Sonnet 5 | $0.00013 | $0.00220 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
hardening-audit 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 11d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read all project markdown documents and examine the codebase to ground in the project's actual stack, dependencies, and deployment architecture.
Hardening Audit
1. HTTP Security Headers
Evaluate each header against the specific architecture — what the app embeds, loads, and connects to:
| Header | Check |
|---|---|
Content-Security-Policy |
Does the CSP account for every external resource? Inline scripts? Fonts? Iframes? report-uri configured? |
Strict-Transport-Security |
HSTS set with max-age, includeSubDomains, and preload considered? |
X-Content-Type-Options |
nosniff set? |
X-Frame-Options |
Appropriate framing policy? DENY or SAMEORIGIN? |
Referrer-Policy |
Balances analytics needs with privacy? |
Permissions-Policy |
Disables browser features not used (camera, microphone, geolocation)? |
Cross-Origin-Opener-Policy |
Set appropriately for the isolation model? |
Cross-Origin-Resource-Policy |
Set on served assets? |
2. Input Validation Boundaries
For every entry point where untrusted data enters the system:
- API endpoints — What validates request body, query params, path params? Max lengths? Encoding? Type coercion?
- Search queries — What sanitizes before database queries? Before LLM prompt construction? Max query length?
- File uploads / ingestion — What validates file type, size, content? Sandboxed processing?
- Webhook receivers — Signature verification? Replay protection? Idempotency?
- URL parameters — Open redirect prevention? Path traversal?
3. Secret Management
- Where do secrets live? Environment variables, Terraform state, CI config,
.envfiles? - Secret rotation — Is there a schedule? Is rotation possible without downtime?
- Secret scope — Are secrets scoped to the minimum required service? Or does one key unlock everything?
- Secret detection — Is there a pre-commit hook or CI check preventing secret commits?
- Secret exposure — Can secrets appear in error messages, logs, or Sentry traces?
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.
- 11d ago First seen · 102 lines · 63 tokens per session scan A 111a465ae8c0
hardening-audit is a skill published in the GitHub repository rana/skills (1 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,099 once invoked, about $0.0003 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
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
second-pass-review
Independent audit of sanitized specs in workspace/output/. Three parallel LLM-based reviewer roles check structural leakage, content contamination, and behavioral completeness. Run AFTER Layer 5 sanitization, BEFORE implementation handoff.
check-pr
Read-only inspection of a single GitHub PR lifecycle — checks CI, review threads, description sync, and mergeability, and returns PASS or FAIL with per-gate findings. Never invokes the merge button. Use when verifying a PR is ready to merge, polling lifecycle progress, checking mergeability, or babysitting a GitHub PR…
codex-review
Get an independent code review from OpenAI Codex (GPT-5) on uncommitted changes, a branch diff, a PR, or a specific module — returns findings grouped by severity with file:line references. Use when the user says "review this", "review my changes", "check this PR", "what did I miss", or before they commit or merge…