source-command-ready

A workflow for turning an approved task into a recorded READY contract before implementation begins. The contract records the goal, allowed files, conditions, acceptance checks, required verification, sources, and plan.

In plain words
What is it for?
Preparing task specifications, creating or updating task-contract packages, validating the workspace and scope, and marking a task ready for a separate implementation command.
Why use it?
It prevents work from starting with unclear scope or missing approval details. Later changes can be tracked instead of silently changing the agreed task.

Skill for Claude CodeCodex

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 skills/baek-labs/hames/source-command-ready
Any agent
npx skills add baek-labs/hames --skill source-command-ready
Clone the repo
git clone --depth 1 https://github.com/baek-labs/hames

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 392 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.00021 $0.00392
Opus 5 $0.00010 $0.00196
Sonnet 5 $0.00004 $0.00078
Haiku 4.5 $0.00002 $0.00039

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

Security

Grade A, and why

source-command-ready 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.

.codex/skills/source-command-ready/SKILL.md · 25 lines

What it actually says

source-command-ready

Use this skill when the user asks to run /ready <task-id>.

Workflow

  1. 현재 작업 공간과 로컬 규칙을 확정한다.
  2. 사용자 요청에서 목표, 승인된 파일 범위, 불변 조건, 인수 기준, 필수 검증, 요청·승인 출처, planarsenal/task_contract.schema.json에 맞는 입력 JSON으로 구조화한다. 출처는 감사용 메타데이터일 뿐 인증이 아니다.
  3. 아래 helper로 .hames/contracts/_Active/<task-id>/ 패키지를 생성하고 DRAFT -> READY로 전환한다. 기존 패키지의 명세를 갱신하는 경우만 draft를 사용한다. DRAFT 이후의 수정은 AMENDMENT_PENDING이 되고 기존 세션 포인터·증거를 무효화한다.
node arsenal/task_contract.js create --input "<spec-json-path>"
# 기존 초안 갱신 시: node arsenal/task_contract.js draft --input "<spec-json-path>"
node arsenal/task_contract.js ready --workspace "<workspace-path>" --task-id "<task-id>"
  1. contract.json 경로, 상태, 리비전, 명세 해시, 기록된 출처를 보고하고 구현은 시작하지 않는다. 현재 사용자의 별도 /go <task-id> 요청을 기다린다.

contract.json이 정본이며 plan.md는 안내일 뿐이다. 낮은 복잡도 작업은 사용자가 /ready를 직접 호출한 경우가 아니면 기존 흐름을 유지한다. 이 스킬은 Git 작업이나 중요 행동 승인을 자동화하지 않는다.

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 · 25 lines · 21 tokens per session scan A c81bdcc33228

Subscribe to this mod's changes

source-command-ready is a skill published in the GitHub repository baek-labs/hames (5 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 392 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-31.

Related

Other skills, from other repositories

代码审查员

专业代码审查专家,提供建设性、可操作的反馈,聚焦正确性、可维护性、安全性和性能,而非代码风格偏好。.

KongFangXun/sofagent · 40 tokens

release-gate-loop

发版前自动验证闸门——V 验证 + F 修复循环(verdict FAIL → F 改代码 → 跑 audit → V 重验),最大 3 轮直到 PASS。纯只读验证 + 最小修复。.

KongFangXun/sofagent · 59 tokens

fresh-eyes-loop

发布后独立质量循环——A/B 双盲 12 视角 fresh-eyes 审查 + 修复 + 验证,每轮新 session 保证零上下文,连续 2 轮无 P0/P1 即停。.

KongFangXun/sofagent · 58 tokens

sofagent-fde

前线部署与知识工程专家。梳理企业业务流、识别 AI 节点、构建 ontology 本体数据、交付离场。 部署完成后转为持续优化模式(sustain),自动读 audit 报告趋势生成优化报告。 不写应用代码——把企业业务规则、组织架构、系统边界转译成 sofagent 的数据层和约束层。.

KongFangXun/sofagent · 93 tokens

sofagent-audit

收到用户任务后,不要自己执行——用 Bash tool 把任务交给 DeepAgents 编排引擎:.

KongFangXun/sofagent · 43 tokens

sofagent

FDE Skill——帮 FDE(前线部署工程师)更好完成企业 AI 落地的方法论 Skill。约束 Agent 行为、审计每次变更、沉淀经验。 底层实现叫约束层——一个层四种能力:注入·审计·回溯·进化。FORGE 自迭代工具链是内部开发工具。 内置持续优化模式(sustain),自动读 audit 报告趋势生成优化报告。.

KongFangXun/sofagent · 108 tokens