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/dev-gom/claude-code-marketplace/checklistgit clone --depth 1 https://github.com/Dev-GOM/claude-code-marketplaceWhat 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.00016 | $0.02649 |
| Opus 5 | $0.00008 | $0.01324 |
| Sonnet 5 | $0.00003 | $0.00530 |
| Haiku 4.5 | $0.00002 | $0.00265 |
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 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Quality Gates Checklist
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
⚠️ 커맨드 구분: 이것은 플러그인 커맨드 (/spec-kit:checklist)입니다. 정보 수집과 사용자 논의를 담당합니다. 실제 파일 생성/업데이트는 GitHub Spec-Kit CLI 커맨드 (/speckit.checklist)가 수행합니다.
🌐 언어 지시사항: 이 명령어를 실행할 때는 사용자의 시스템 언어를 자동으로 감지하여 해당 언어로 모든 안내, 체크리스트, 리포트, 출력을 제공해야 합니다. 시스템 환경 변수(LANG, LC_ALL 등)나 사용자의 이전 대화 패턴을 분석하여 언어를 판단하세요.
헌법에 정의된 품질 게이트를 실행하여 코드가 프로젝트 기준을 충족하는지 확인합니다.
Purpose
다음을 검증합니다:
- 코드 품질 기준
- 테스트 커버리지
- 성능 예산
- 보안 요구사항
- 접근성 기준
- 문서화 완성도
Step 1: Load Quality Gates
헌법에서 품질 게이트 읽기:
cat .specify/memory/constitution.md
"Quality Gates" 섹션 찾기:
- Pre-Merge Checklist
- Pre-Release Checklist
Step 2: Run Automated Checks
자동화 가능한 체크 실행:
Code Quality
# Lint
npm run lint
# or
eslint src/
# Format check
npm run format:check
# or
prettier --check src/
Result: ✅ Pass / ❌ Fail
Testing
# Run tests
npm test
# Coverage report
npm run test:coverage
Expected: Coverage >= 80% Actual: [%]% Result: ✅ Pass / ❌ Fail
Type Checking (TypeScript)
npm run type-check
# or
tsc --noEmit
Result: ✅ Pass / ❌ Fail
Performance
# Build
npm run build
# Bundle size check
npm run analyze
Expected: < 50 KB gzipped Actual: [N] KB Result: ✅ Pass / ❌ Fail
Security
# Dependency audit
npm audit
# Check for vulnerabilities
npm audit --audit-level=moderate
Result: ✅ Pass / ❌ Fail ([N] vulnerabilities)
Step 3: Manual Checks
자동화할 수 없는 항목 확인:
Accessibility
- Lighthouse Accessibility Score > 90
- Keyboard navigation tested
- Screen reader compatible
- Color contrast meets WCAG AA
How to check:
# Lighthouse CI
npm run lighthouse
# or
lighthouse https://localhost:3000 --view
Documentation
- README updated
- API documentation complete
- Changelog updated
- Migration guide (if breaking changes)
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 · 410 lines · 16 tokens per session scan A d90b571eb1f9
checklist is a command published in the GitHub repository Dev-GOM/claude-code-marketplace (97 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 2,649 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.