accept

A command that records a user's explicit acceptance of a reviewed task. Acceptance means the user has taken responsibility for the result; passing tests or an agent's self-review does not count.

In plain words
What is it for?
Use /accept with a task ID when the current user has reviewed and accepted a task. It records the acceptance but does not archive, commit, push, or deploy anything.
Why use it?
It separates human approval from automated checks and prevents a task from being treated as accepted without a direct user request.

Command for Claude Code

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/baek-labs/hames/accept
Clone the repo
git clone --depth 1 https://github.com/baek-labs/hames

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 152 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.00016 $0.00152
Opus 5 $0.00008 $0.00076
Sonnet 5 $0.00003 $0.00030
Haiku 4.5 $0.00002 $0.00015

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

Security

Grade A, and why

accept 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.

.claude/commands/accept.md · 16 lines

What it actually says

/accept

사용법: /accept <task-id>

테스트 통과, 증거 생성, 모델의 자가 평가를 사용자 인수로 간주하지 않는다. 현재 사용자가 이 커맨드를 명시적으로 요청했고 계약이 REVIEW인 경우에만 실행한다.

node arsenal/task_contract.js accept --workspace "<workspace-path>" --task-id "<task-id>" --approval "current-user:/accept <task-id>"

결과로 ACCEPTED 상태와 인수 출처를 보고한다. 인수는 자동 archive, commit, push, deploy를 실행하지 않는다.

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 · 16 lines · 16 tokens per session scan A af88c4645acf

Subscribe to this mod's changes

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