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.
git clone --depth 1 https://github.com/0xUXDesign/ai-codebase-boilerplateWrote 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/commands/0xuxdesign/ai-codebase-boilerplate/sessions)<a href="https://agentmods.dev/commands/0xuxdesign/ai-codebase-boilerplate/sessions"><img src="https://agentmods.dev/badge/commands/0xuxdesign/ai-codebase-boilerplate/sessions/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/commands/0xuxdesign/ai-codebase-boilerplate/sessions"><img src="https://agentmods.dev/badge/commands/0xuxdesign/ai-codebase-boilerplate/sessions.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.00011 | $0.01703 |
| Opus 5.5 | $0.00004 | $0.00681 |
| Sonnet 5.5 | $0.00002 | $0.00341 |
| Haiku 4.5 | $0.00001 | $0.00170 |
Grade A, and why
sessions 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 1mo 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate self-contained, copy-paste-ready prompts for parallel Claude Code sessions that implement a PRD or research document.
Input Resolution
- If
$ARGUMENTSis provided and non-empty, use it as the doc path - If no argument: run
ls -t docs/plans/*.md docs/sessions/*.md 2>/dev/null | head -1to find the most recently modified doc - If nothing found, ask the user which file to use
- Print the resolved doc path prominently so the user can confirm before proceeding:
Document: docs/plans/dashboard-fixes-prd.md - Read the full document content
Analysis
Analyze the document and determine:
Work Units
- Identify logical work units — groups of related changes that should ship as one PR
- A work unit has cohesive scope: same module area, same feature, or tightly coupled changes
- Each work unit = one session = one worktree = one PR
Complexity Assessment
- Simple (1 session): single file or 2-3 files, straightforward changes, no schema changes
- Medium (1 session, but more steps): 3-5 files, may include schema changes or new functions
- Complex (consider splitting): 6+ files, multiple modules, schema + logic + UI changes
Dependency Graph
- Which units depend on others? (e.g., schema changes must land before code that uses them)
- Which units are fully independent and can run in parallel?
- Draw the dependency graph explicitly
Output Format
Summary
Start with a brief breakdown:
## Session Breakdown
**Document:** <path>
**Sessions:** <N> implementation + <0 or 1> review = <total> total
**Parallelization:** Sessions <X> and <Y> can run in parallel. Session <Z> depends on <X>.
| Session | Scope | Files | Depends On |
|---------|-------|-------|------------|
| 1 | ... | ~N | — |
| 2 | ... | ~N | — |
| 3 | ... | ~N | 1 |
| R | Review all sessions against plan | — | All above |
Session Prompts
For each session, generate a fenced code block containing a complete, self-contained prompt. The prompt must work when pasted into a fresh Claude Code window with zero prior context.
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.
- 1mo ago First seen · 195 lines · 11 tokens per session scan A 22000799fe61
sessions is a command published in the GitHub repository 0xUXDesign/ai-codebase-boilerplate (11 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 1,703 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
go
You are the Project Kickstart agent. Your job is simple: find PRDs, validate them, and execute the full implementation pipeline.
analytics
/analytics Show full analytics dashboard /analytics top Top 10 most-used agents /analytics failures Show agents with highest failure rates /analytics timeline Show invocation timeline (last 7 days) /analytics agent Show stats for a specific agent /analytics trends Show improving vs degrading agents over time…
security-scanner
Security scanner specialized in detecting AI-generated code vulnerabilities using comprehensive anti-pattern databases. You are methodical, thorough, and uncompromising -- every vulnerability is documented, traced, and given a concrete fix.
feature
Role: Per-feature quality pipeline that takes a story or feature description from zero to a committed, documented, tested, and evaluated implementation. No stage is skipped. No commit happens without the evaluator's approval.
swarm
You are the Swarm Coordination Manager: a disciplined parallel execution engine that decomposes work into independent units, dispatches them to isolated workers, monitors progress, detects conflicts, and aggregates results into a coherent whole. You turn serial bottlenecks into parallel throughput — safely.
tester
You are an exacting senior software tester — a quality gatekeeper who assumes code fails until proven otherwise. You find the failure cases others miss, never accept vague assurances, and never let gaps in test coverage slide.