Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JeremyDev87/codingbuddynpx agentmods add commands/jeremydev87/codingbuddy/checklistWrote 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/jeremydev87/codingbuddy/checklist)<a href="https://agentmods.dev/commands/jeremydev87/codingbuddy/checklist"><img src="https://agentmods.dev/badge/commands/jeremydev87/codingbuddy/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/commands/jeremydev87/codingbuddy/checklist"><img src="https://agentmods.dev/badge/commands/jeremydev87/codingbuddy/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.00000 | $0.00303 |
| Opus 5.5 | $0.00000 | $0.00121 |
| Sonnet 5.5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
checklist 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.
What it actually says
Checklist Generator
Purpose
Generate contextual checklists based on file patterns and domains for comprehensive code review.
Available Domains
| Domain | Description |
|---|---|
| security | Authentication, authorization, input validation, XSS/CSRF |
| accessibility | WCAG 2.1 AA, ARIA, keyboard navigation, focus management |
| performance | Bundle size, code splitting, rendering optimization |
| testing | Test coverage, TDD, edge cases, integration tests |
| code-quality | SOLID principles, DRY, complexity, design patterns |
| seo | Metadata, structured data, social sharing |
Usage
/codingbuddy:checklist [files] [domains]
Examples:
/codingbuddy:checklist src/auth/*.ts security/codingbuddy:checklist src/components/*.tsx accessibility performance/codingbuddy:checklist(auto-detect from recent changes)
Legacy bare
/checklistis deprecated. See Migration Guide.
MCP Integration
If CodingBuddy MCP server is available, call:
generate_checklist({ files: ["src/auth/*.ts"], domains: ["security"] })
This generates domain-specific checklists based on file patterns and import analysis.
Auto-Detection
When no files are specified, the checklist generator will:
- Analyze recently modified files
- Detect relevant domains from imports and patterns
- Generate appropriate checklists automatically
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 · 45 lines · 0 tokens per session scan A 384183ae3a0f
checklist is a command published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 303 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-30.
Other commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.