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 agentmods add skills/codeverbojan/claude-code-kickstart/securing-codenpx skills add codeverbojan/claude-code-kickstart --skill securing-codegit clone --depth 1 https://github.com/codeverbojan/claude-code-kickstartWhat 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 | $0.00039 | $0.00544 |
| Opus 5 | $0.00019 | $0.00272 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
securing-code 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 yesterday.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure Code Patterns
API Route Handler Order
Always follow this sequence in every server-side handler:
1. Auth check
2. CSRF check (mutations only)
3. Input validation (schema-based)
4. Business logic (parameterized queries only)
5. Response
Non-Obvious Rules
- CSRF tokens on ALL mutations (POST, PUT, DELETE) — not just forms
- Rate limit auth endpoints specifically (login, reset, signup)
sameSite=stricton session cookies, notlax- Set
X-Content-Type-Options: nosniff— prevents MIME sniffing attacks - Audit log sensitive operations (rate changes, user management, role changes)
Supply Chain
Pin versions, block scripts, enforce soak periods. These are enforceable guards, not advice — configure them in the project.
Node.js (.npmrc)
# Block postinstall scripts by default (would have stopped the Axios attack)
ignore-scripts=true
# 7-day soak period — don't install packages published in the last week
minimum-release-age=10080
# Pin exact versions — no ^ or ~
save-exact=true
# Enforce peer deps and run audit on every install
strict-peer-dependencies=true
audit=true
After adding ignore-scripts=true, explicitly allow trusted scripts:
pnpm config set allow-scripts "esbuild,sharp,prisma"
Python (pip)
# Pin with hashes for integrity verification
pip install --require-hashes -r requirements.txt
# Generate pinned requirements with hashes
pip-compile --generate-hashes requirements.in
Go
# Verify module checksums against public transparency log
GONOSUMCHECK= GOFLAGS=-mod=readonly go build ./...
Rust
# Cargo.toml — use exact versions
[dependencies]
serde = "=1.0.210"
# Audit for known vulnerabilities
cargo audit
When adding ANY new dependency
- Check: maintainer count, download volume, last publish date
- Review:
postinstall/ build scripts in the package - Verify: no phantom transitive dependencies added
- Wait: prefer packages with 7+ days since last publish
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.
- yesterday First seen · 94 lines · 39 tokens per session scan A 6df09c5fa9d9
securing-code is a skill published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 544 once invoked, about $0.0002 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
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
swiftui-debugging
Use when debugging SwiftUI issues in this macOS app — views not updating, layout problems, unnecessary re-renders, state ownership bugs, Preview crashes, or NSHostingView/NSPanel quirks. Covers both general SwiftUI debugging and macOS-specific patterns.