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/checkgit 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.00009 | $0.00898 |
| Opus 5 | $0.00005 | $0.00449 |
| Sonnet 5 | $0.00002 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade C, and why
check scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check spec-kit Installation & Project Status
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
🌐 언어 지시사항: 이 명령어를 실행할 때는 사용자의 시스템 언어를 자동으로 감지하여 해당 언어로 모든 안내, 설치 가이드, 출력을 제공해야 합니다. 시스템 환경 변수(LANG, LC_ALL 등)나 사용자의 이전 대화 패턴을 분석하여 언어를 판단하세요.
spec-kit 환경이 올바르게 설정되었는지 확인합니다.
Step 1: CLI Installation Check
먼저 uv가 설치되어 있는지 확인:
uv --version
설치됨:
✅ uv: Installed (version X.X.X)
미설치:
❌ uv: Not installed
Install uv:
- macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh
- Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Next: 설치 후 터미널 재시작 → /spec-kit:check 재실행
다음으로 specify CLI가 설치되어 있는지 확인:
uv tool list | grep specify
설치됨:
✅ specify CLI: Installed
출력 예시:
specify-cli v{version}
- specify.exe
설치가 확인되면 specify check 명령으로 환경을 테스트:
PYTHONIOENCODING=utf-8 specify check
정상 작동 시 마지막에 표시:
Specify CLI is ready to use!
✅ 이 메시지가 보이면 프로젝트 초기화 준비 완료
미설치:
❌ specify CLI: Not installed
(uv tool list에 specify가 없음)
Install specify CLI:
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
Next Steps:
1. 터미널 재시작
2. /spec-kit:init 실행하여 프로젝트 초기화
중요: Git Bash에서는 PYTHONIOENCODING=utf-8 접두사가 필요합니다 (Windows cp949 인코딩 문제 해결)
Step 2: Project Setup Check
CLI가 준비되었다면 프로젝트 초기화 상태 확인:
ls -la .specify/
Initialized:
✅ **Project Setup**
✅ .specify/ directory found
✅ Project is initialized
Existing files:
- constitution.md
- specification.md
- plan.md
- tasks.md
Next: /speckit:specify, /speckit:plan, /speckit:implement
Not Initialized:
ℹ️ **Project Setup**
⚠️ .specify/ not found
⚠️ Project not initialized
Next: /speckit:init
Troubleshooting
"specify: command not found" 또는 인코딩 오류
방법 1: 전체 경로 사용 (가장 확실)
Windows (CMD):
set PYTHONIOENCODING=utf-8 && "%USERPROFILE%\.local\bin\specify.exe" check
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 · 157 lines · 9 tokens per session scan C cbc0a1cc026f
check 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 9 tokens to every session and 898 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.