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 atuljha23/holocron --skill security-checklistgit clone --depth 1 https://github.com/atuljha23/holocronWrote 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/atuljha23/holocron/security-checklist)<a href="https://agentmods.dev/skills/atuljha23/holocron/security-checklist"><img src="https://agentmods.dev/badge/skills/atuljha23/holocron/security-checklist/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/atuljha23/holocron/security-checklist"><img src="https://agentmods.dev/badge/skills/atuljha23/holocron/security-checklist.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.00036 | $0.00943 |
| Opus 5 | $0.00018 | $0.00472 |
| Sonnet 5 | $0.00007 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
security-checklist scanned grade A with 1 finding 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 12d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- [ ] Shell: use argv arrays, never `exec(string)` with user input. Use a safe runner (`execFile`, `subprocess.run([...])`). How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security checklist
Authn / authz
- Authentication check happens on a path the caller can't influence (verified JWT, session cookie with
HttpOnly/Secure/SameSite). - Authorization is explicit in the handler, not implied by routing.
- Role/permission decisions use the server's identity model, never a client-supplied header.
- Multi-tenant check: the resource belongs to the caller's tenant (not just the caller's user).
- No IDOR: object IDs in URLs are checked against ownership, not just existence.
Input validation
- Validated at the edge (handler/controller), not deep in services.
- Schema-based where possible (zod/pydantic/struct tags).
- Every sink is aware of the shape feeding it (SQL parameters, shell args, template context, file paths, HTTP URLs, deserializers).
Injection surfaces
- SQL: parameters only. Never string-concat into a query.
- Shell: use argv arrays, never
exec(string)with user input. Use a safe runner (execFile,subprocess.run([...])). - Path: reject
.., absolute paths, and symlinks that escape the allowed root. - Template: auto-escape on; avoid
raw/|safe; parameterize over string assembly. - Deserializers: never
pickle/yaml.load/evalon untrusted input. - HTML rendering: sanitize + use a framework that auto-escapes; beware
dangerouslySetInnerHTML.
Secrets
- Not in source.
- Not logged. Scrub before logging (redact keys like
password,token,secret,auth). - Read from env or a secrets manager.
- Rotated when in doubt.
Sessions / cookies
-
HttpOnly,Secure,SameSite=Lax(orStrictwhen tighter is fine). - Session rotates on privilege change (login, logout, role change).
- Logout invalidates server-side, not just client-side.
Crypto
- Use the platform library. Never roll your own.
- MD5 / SHA-1 are NOT for security. Use SHA-256+, bcrypt/argon2 for passwords.
- Encryption in authenticated mode (AES-GCM), never ECB.
- RNG: cryptographic (
crypto.randomBytes/secrets.token_*), neverMath.random. - Secrets compared in constant time where applicable.
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.
- 12d ago First seen · 78 lines · 36 tokens per session scan A 1e9ba6d3e255
security-checklist is a skill published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 943 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deslop
Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or…
improve-architecture
Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to…
llm-gate
LLM-powered quality verification using prompt hooks. Validates commit messages, code patterns, and conventions using AI before allowing operations. Use to set up intelligent guardrails.
smart-commit
Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.
batch-rewrite-pattern
Cascade the same edit pattern across N files safely. Use when applying the same refactor to multiple files (e.g. swap import paths across 11 scripts, rename a symbol, migrate a call signature). Detects the common-shape-across-files situation and turns an N-file cascade into a planned audit → apply → verify workflow…
code-review
Reviews code for bugs, style, and best practices. Use when reviewing PRs or checking code quality.