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/initgit 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.05995 |
| Opus 5 | $0.00005 | $0.02998 |
| Sonnet 5 | $0.00002 | $0.01199 |
| Haiku 4.5 | $0.00001 | $0.00600 |
Grade D, and why
init scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get update && sudo apt-get install git -y 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.
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.
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" How it starts
The opening of the file, as written. The whole thing — 899 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize spec-kit Project
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty). The user input is the project name.
🌐 언어 지시사항: 이 명령어를 실행할 때는 사용자의 시스템 언어를 자동으로 감지하여 해당 언어로 모든 안내, 설치 가이드, 초기화 메시지, 출력을 제공해야 합니다. 시스템 환경 변수(LANG, LC_ALL 등)나 사용자의 이전 대화 패턴을 분석하여 언어를 판단하세요.
GitHub Spec-Kit을 사용하여 명세 주도 개발(SDD) 프로젝트를 초기화합니다.
Step 0: Check Existing Installation
먼저 .specify/ 디렉토리가 이미 존재하는지 확인:
ls -la .specify/
이미 초기화된 경우:
AskUserQuestion 도구를 사용하여 사용자에게 확인:
{
"questions": [{
"question": "이미 spec-kit 프로젝트가 초기화되어 있습니다. 어떻게 하시겠습니까?",
"header": "재초기화",
"multiSelect": false,
"options": [
{
"label": "새로 초기화 (기존 데이터 삭제)",
"description": ".specify/ 폴더를 삭제하고 처음부터 다시 초기화합니다. 기존의 constitution, specification, plan, tasks 파일이 모두 삭제됩니다."
},
{
"label": "취소 (기존 설정 유지)",
"description": "초기화를 취소하고 기존 spec-kit 프로젝트를 그대로 사용합니다."
}
]
}]
}
- "새로 초기화" 선택 시: Step 1으로 진행
- "취소" 선택 시: 아래 "Step 0.1: 기존 프로젝트 상태 확인"으로 진행
초기화되지 않은 경우:
바로 Step 1으로 진행
Step 0.1: 기존 프로젝트 상태 확인
사용자가 "취소"를 선택한 경우, 현재 프로젝트의 상태를 확인하고 다음 작업을 안내합니다.
1. 프로젝트 구조 표시
tree -L 2 .specify/
또는 Windows의 경우:
ls -R .specify/ | head -30
2. 각 파일 존재 여부 확인
ls -lh .specify/memory/constitution.md 2>/dev/null && echo "✅ Constitution" || echo "❌ Constitution"
ls -lh .specify/memory/specification.md 2>/dev/null && echo "✅ Specification" || echo "❌ Specification"
ls -lh .specify/memory/plan.md 2>/dev/null && echo "✅ Plan" || echo "❌ Plan"
ls -lh .specify/memory/tasks.md 2>/dev/null && echo "✅ Tasks" || echo "❌ Tasks"
3. 진행 상태 분석 및 다음 작업 안내
파일 존재 여부에 따라 다음 작업을 안내:
Constitution이 없는 경우:
📋 현재 상태: spec-kit이 초기화되었지만 아직 프로젝트 원칙이 정의되지 않았습니다.
🚀 다음 작업:
/spec-kit:constitution
프로젝트의 핵심 원칙과 기준을 정의하세요.
Constitution은 있지만 Specification이 없는 경우:
📋 현재 상태: 프로젝트 원칙이 정의되었습니다.
✅ 완료: Constitution
❌ 대기: Specification → Plan → Tasks → Implementation
🚀 다음 작업:
/spec-kit:specify <기능 설명>
구현할 기능의 요구사항을 정의하세요.
예: /spec-kit:specify Add user authentication with OAuth2
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 · 899 lines · 9 tokens per session scan D f27b6b2c387e
init 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 5,995 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.