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 commands/ds1/boilerplate.md/initgit clone --depth 1 https://github.com/ds1/boilerplate.mdWhat 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.00000 | $0.00619 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
init 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 2d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Project Structure
Scaffold the standard file structure for a new project.
Steps
-
Detect project context:
- Read
package.jsonor other config files to determine project name and description - Check what already exists — don't overwrite existing files
- Determine the tech stack from existing files
- Read
-
Create the following files if they don't exist:
.gitignore— with at minimum:node_modules/ .env* .vercel/ .supabase/ *.pem *.key .DS_Store Thumbs.dbAdd framework-specific entries based on detected stack (e.g.,
.next/for Next.js,dist/for builds)..gitattributes:* text=autoSTATUS.md:# Project Status Last updated: YYYY-MM-DD HH:MM ## In Progress _None yet_ ## Blockers _None_ ## Up Next - [ ] Initial project setup ## Recently CompletedCHANGELOG.md:# Changelog All notable changes to this project are documented here. ## [Unreleased] ### Added - Initial project setupREADME.md— with:- Project name (from package.json or directory name)
- Brief description (ask user if not obvious)
- Tech stack
- Setup/install instructions (
npm install, env vars needed) - Development commands (
npm run dev, etc.) - Deployment info if detectable
_planning/directory with:backlog.md— empty template:# Backlog ## High Priority ## Medium Priority ## Low Priority / Ideasplans/— empty directory (create with a.gitkeep)
CLAUDE.md— if it doesn't exist, create a starter:# Project Name Brief description. ## Commands - Dev: `npm run dev` - Build: `npm run build` - Lint: `npm run lint` ## Architecture <!-- Add project structure and key patterns here --> ## Current Status See `STATUS.md` for current work and `CHANGELOG.md` for completed milestones.If CLAUDE.md already exists, just ensure it has the STATUS.md/CHANGELOG.md reference line.
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.
- 2d ago First seen · 109 lines · 0 tokens per session scan A f204fc4668dc
init is a command published in the GitHub repository ds1/boilerplate.md (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 619 tokens. 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 commands, from other repositories
create-pr
Create a pull request following the official template.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
learn
Command "learn" from chohra-med/expo_boilerplate, covering command: learn — the learning loop (feedback → rules), when to run it, invocation, the loop (6 steps) and 1 — capture.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
audit
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.
build
Command "build" from chohra-med/expo_boilerplate, covering command: build — run the sdd pipeline over tasks.md, invocation, per-task cycle, gates (constitution) and output.