phase-4-api

A compatibility command for managing phase-based work in the demokit /pipeline process. It represents Phase 4, where features and APIs are developed.

In plain words
What is it for?
Use it to check the current phase, work on Phase 4, and advance to the next phase after the required checks are complete.
Why use it?
It gives projects that still use this command a guide for following the newer pipeline process. It also reminds you to check deliverables, tests, reviews, and risks before moving on.

Command

Part of the demokit plugin — 23 skills, 19 commands, 15 agents, 10 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/demodev-lab/claude-code-plugin-demokit/phase-4-api
Clone the repo
git clone --depth 1 https://github.com/demodev-lab/claude-code-plugin-demokit

Or install demokit, the plugin that ships this one along with the rest of its 23 skills, 19 commands, 15 agents, 10 hooks.

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 167 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00167
Opus 5 $0.00017 $0.00084
Sonnet 5 $0.00007 $0.00033
Haiku 4.5 $0.00003 $0.00017

Measured 2d ago against content hash 53b8d6c0f78c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

phase-4-api 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.

commands/phase-4-api.md · 27 lines

What it actually says

/phase-4-api (Compatibility Alias)

이 명령은 demokit /pipeline 기반 phase 운영을 위한 호환 가이드입니다.

현재 단계

  • Phase 4: Feature/API

권장 명령

  1. /pipeline status
  2. 현재 단계 작업 수행
  3. 완료 시 /pipeline next

체크포인트

  • 산출물/테스트/리뷰 기준을 충족했는지 확인
  • 다음 단계 전환 전에 주요 리스크를 기록
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.

  1. 2d ago First seen · 27 lines · 35 tokens per session scan A 53b8d6c0f78c

Subscribe to this mod's changes

phase-4-api is a command published in the GitHub repository demodev-lab/claude-code-plugin-demokit (2 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 167 once invoked, about $0.0002 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-31.