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 skills add sangrokjung/claude-forge --skill cc-dev-agentgit clone --depth 1 https://github.com/sangrokjung/claude-forgeWrote 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/skills/sangrokjung/claude-forge/cc-dev-agent)<a href="https://agentmods.dev/skills/sangrokjung/claude-forge/cc-dev-agent"><img src="https://agentmods.dev/badge/skills/sangrokjung/claude-forge/cc-dev-agent.svg" alt="Measured on agentmods" 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.00045 | $0.01189 |
| Opus 5 | $0.00023 | $0.00594 |
| Sonnet 5 | $0.00009 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade B, and why
cc-dev-agent scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- 설정 위치: `~/.claude/settings.json`의 `env` 또는 셸 환경변수 How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Agent
Claude Code를 활용한 Spec-Driven 개발 워크플로우 및 Context Engineering 가이드.
핵심 원칙
- Context Engineering: 제한된 컨텍스트 윈도우에서 토큰 유용성 최적화
- Spec-Driven: 코드 전에 스펙(spec.md) 먼저 → 반복 수정 8배 감소
- TDD Loop: Red(테스트) → Green(구현) → Refactor
- Sub-agents 활용: Explore, Plan 에이전트로 작업 분산
- 작성-검증 분리:
/clear후 새 눈으로 검증 (Boris 원칙)
병렬 개발 (Agent Teams v6)
Git Worktree 기반 병렬 개발은 레거시. Agent Teams가 팀 생성/정리를 자동 처리.
전제조건
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS를1로 설정- 설정 위치:
~/.claude/settings.json의env또는 셸 환경변수
사용법
/orchestrate --type feature # 기능 구현
/orchestrate --type bugfix # 버그 수정
/orchestrate --type refactor # 리팩토링
→ 상세 가이드: references/sub-agents.md
개발 완료 후 워크플로우 (Boris 방식)
"Give Claude a way to verify its work. If Claude has that feedback loop, it will 2-3x the quality."
핵심 플로우
/orchestrate (선택) → 개발 → /handoff-verify
→ /sync-docs (머지 전 문서 동기화 의무)
→ /commit-push-pr --merge
→ /web-checklist
단계별 역할
| 단계 | 명령어 | 이유 |
|---|---|---|
| 1 | /orchestrate (선택) |
Agent Teams 병렬 개발 |
| 2 | 개발 | 기능 구현 |
| 3 | /handoff-verify |
의도 문서화 + fresh context 자동 검증 (v6 통합) |
| 4 | /sync-docs |
머지 전 문서 동기화 (의무 게이트) — 문서 변경분이 머지 커밋에 포함됨 |
| 5 | /commit-push-pr --merge |
커밋 & PR & 머지 (v7: sync-docs 게이트 내장 — 4단계 누락 시 자동 실행) |
| 6 | /web-checklist |
웹 테스트 체크리스트 |
→ 상세 가이드: references/post-dev-workflow.md
Context Engineering
| 명령어 | 용도 | 사용 시점 |
|---|---|---|
/clear |
컨텍스트 완전 초기화 | 새 Task, 에러 루프 탈출, 검증 전 |
/compact |
대화 요약 압축 | 60% 도달 시 |
/context |
현재 사용량 확인 | 복잡한 작업 중 수시 체크 |
→ 상세 가이드: references/context-engineering.md
Sub-agents
| 유형 | 용도 |
|---|---|
Explore |
빠른 코드베이스 검색 (Read-only) |
Plan |
구현 계획 설계 |
병렬 처리: 최대 10개 동시 실행
→ 상세 가이드: references/sub-agents.md
개발 5단계
Phase 1: 초기화 → CLAUDE.md 생성
Phase 2: 기획 → spec.md, prompt_plan.md 작성
Phase 3: 구현 → TDD Loop 반복 (핵심)
Phase 4: 검증 → 스펙 대조, 코드 리뷰
Phase 5: 배포 → 보안 검토, 최종 점검
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 139 lines · 45 tokens per session scan B 2b9607f3fc30
cc-dev-agent is a skill published in the GitHub repository sangrokjung/claude-forge (824 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 1,189 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.