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/remembergit 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.00453 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade B, and why
remember scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Tool permission** (goes in `~/.claude/settings.json` under `permissions.allow`): What it actually says
Remember Global Preference
Save a global preference or behavior based on the user's natural language description.
Usage
/remember <description of desired behavior>
Steps
-
Parse the user's description and classify it:
Tool permission (goes in
~/.claude/settings.jsonunderpermissions.allow):- "allow rm commands" -> add
Bash(rm:*) - "allow docker" -> add
Bash(docker:*) - "let me use bun" -> add
Bash(bun:*) - Any request to auto-approve a specific command or tool
Behavioral instruction (goes in
~/.claude/CLAUDE.md):- "always run tests after changes"
- "prefer bun over npm"
- "don't auto-commit"
- "use tabs not spaces"
- Any preference about how Claude should work, communicate, or make decisions
Project memory (goes in the current project's
memory/MEMORY.md):- "this project uses port 4000"
- "the API is at /v2 not /v1"
- Any fact specific to the current project, not global
- "allow rm commands" -> add
-
Show the user:
- What will be saved
- Where it will be saved (file path)
- The exact content being added
-
Save it to the appropriate file:
- settings.json: Add to the
permissions.allowarray - CLAUDE.md: Append under the most relevant existing section, or create a new
## User Preferencessection if none fits - memory/MEMORY.md: Append under a relevant heading or create one
- settings.json: Add to the
-
Confirm: "Saved to [file]. This will persist across all future sessions."
Classification Priority
If unclear, default to ~/.claude/CLAUDE.md. Behavioral instructions are the most common case.
By @ds1 — boilerplate.md
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 · 48 lines · 0 tokens per session scan B cc7a7d23e26a
remember 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 453 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
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.
board-csk
Team board — see who holds which item, claim one, hand it over, complete it.