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 komluk/scaffolding --skill security-review-checklistsgit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/security-review-checklists)<a href="https://agentmods.dev/skills/komluk/scaffolding/security-review-checklists"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/security-review-checklists/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/komluk/scaffolding/security-review-checklists"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/security-review-checklists.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.00065 | $0.00971 |
| Opus 5 | $0.00032 | $0.00485 |
| Sonnet 5 | $0.00013 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
security-review-checklists 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 9d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OWASP Top 10 Checklist
| Vulnerability | Check |
|---|---|
| Injection | Parameterized queries, input validation |
| Broken Auth | Session management, MFA where needed |
| Sensitive Data | Encryption, no logging PII |
| XXE | Disable external entities in XML |
| Broken Access | Authorization on all endpoints |
| Misconfiguration | Secure defaults, no debug in prod |
| XSS | Output encoding, CSP headers |
| Insecure Deserialization | Validate before deserialize |
| Vulnerable Components | Check dependencies |
| Logging | Audit trails, no sensitive data in logs |
STRIDE Threat Modeling
| Threat | Check For |
|---|---|
| Spoofing | Authentication weaknesses |
| Tampering | Data integrity issues |
| Repudiation | Missing audit logs |
| Info Disclosure | Data exposure risks |
| Denial of Service | Rate limiting gaps |
| Elevation | Authorization bypasses |
Authentication Review
| Aspect | Requirements |
|---|---|
| Password policy | Min length, complexity, no common passwords |
| Token handling | Secure storage, expiration, refresh |
| Session mgmt | Timeout, invalidation, secure cookies |
| MFA | Available for sensitive operations |
Authorization Review
| Pattern | Check |
|---|---|
| RBAC | Roles properly defined and enforced |
| Resource access | Per-resource authorization |
| Least privilege | Minimal permissions granted |
| Default deny | Explicit grants required |
Data Protection Review
| Data State | Requirement |
|---|---|
| In transit | TLS 1.2+ |
| At rest | AES-256 encryption |
| In logs | No PII, no secrets |
| In errors | No stack traces to users |
Compliance Quick Check
| Framework | Key Requirements |
|---|---|
| GDPR | Consent, data minimization, deletion |
| HIPAA | PHI encryption, access controls |
| PCI DSS | Cardholder data protection |
| SOC 2 | Security controls, audit |
Input Validation Rules
| Data Type | Validation |
|---|---|
| Regex pattern, max 255 chars | |
| Password | Min 8 chars, upper + lower + number + special |
| URL | Protocol whitelist (https only) |
| File upload | Extension whitelist, MIME check, size limit |
| IDs | UUID format or positive integer |
| Free text | Max length, HTML sanitization |
What ships with it
2 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.
- 9d ago First seen · 125 lines · 65 tokens per session scan A 622260585de0
security-review-checklists is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 971 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-30.
Other skills, from other repositories
turnstile-loop-start
Starts a goal-directed loop run -- asks for mode, initialises state.json, then dispatches loop-runner repeatedly until the success condition is met, max-iterations is reached, or an unrecoverable error occurs.
turnstile-loop-status
Reads turnstile/loops/ /state.json and renders the current phase, status, and full iteration history in the terminal.
turnstile-conversate
Entry point for natural-language turnstile requests -- classifies the message against board state, then answers directly or invokes the one matching skill (brainstorm, quick, refine, spec, sprint-plan, work, review, breakdown, drop, systematic-debugger, code-reviewer).
turnstile-work
Implements one sprint ticket via TDD and the turnstile-coder agent, checking the brain first. Dispatched by /turnstile:work or conversate routing only.
turnstile-brain-init
Opt-in bulk bootstrap of turnstile/code/ -- one linked note per source file. The default pipeline is lazy (code notes only for ticket-touched files, written when the ticket passes review); this is the eager exception. Dispatched by /turnstile:brain-init only.
turnstile-brain
Vault layout, the shared note format, and the check-the-brain-first mandate. Auto-loads whenever any turnstile skill starts new work or /turnstile:review is about to commit.