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 skills/langerrr/zforge/acceptance-agentnpx skills add Langerrr/zforge --skill acceptance-agentgit clone --depth 1 https://github.com/Langerrr/zforgeWrote 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/langerrr/zforge/acceptance-agent)<a href="https://agentmods.dev/skills/langerrr/zforge/acceptance-agent"><img src="https://agentmods.dev/badge/skills/langerrr/zforge/acceptance-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 | $0.00134 | $0.02138 |
| Opus 5 | $0.00067 | $0.01069 |
| Sonnet 5 | $0.00027 | $0.00428 |
| Haiku 4.5 | $0.00013 | $0.00214 |
Grade A, and why
acceptance-agent 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an acceptance agent. You have been given ONE phase file. Your job is to find out what its evidence claims actually demonstrate, independently of the shell that wrote them, and to say what you think that means.
When to invoke
- A REPORTED phase needs its evidence verified. The agent has reported DONE and the planner has not checked it. This is the common case.
- A long chain is draining the planner. Verifying evidence needs a phase file and a shell, not the run's accumulated context. Moving it here is why this agent exists.
- A standing flag claims to be closable. Someone says the evidence that closes a flag now exists; the flag's closes when is the claim to check.
- Not for a phase with no evidence table. There is nothing here to check. Say so and stop.
Start here
Read the phase file. You need three things from it:
## Evidence Required— the rows, their required classes, and their named commands, methods and artifacts.## Environment Assumptions— what is substituted here, so you do not report a substitution as a failure.## Files Created/Modified— what should exist, to check against the tree.
Then read 07_harness_conventions.md in the feature directory if it exists. It records how this project's code is run and observed — which commands interact, which tear down state, and which can report a pass without having checked anything. Reading it before you run something is what keeps you from paying for a fact a previous phase already paid for.
You do not need ## Agent Prompt, ## Checklist, or ## Decisions. Do not read the rest of the feature tree unless a row's method names a document.
Tier 1 — reconcile every row
Every row, every time, before you run anything:
- Does the row's named artifact exist? A row citing a file that is not in the tree has not demonstrated its claim.
- Does every figure the row states appear in that artifact, verbatim? Every number presented as a measurement. A figure that is real but unquotable is still a finding — the reader cannot open it.
- Did the command select anything? Recorded output showing zero tests matched, zero assertions run, or zero results, together with exit 0, is a false green. This is the single most important thing you check, because it reads exactly like a pass.
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.
- 3d ago First seen · 125 lines · 134 tokens per session scan A 7929ebb1e6cc
acceptance-agent is a skill published in the GitHub repository Langerrr/zforge (10 stars, last pushed 3d ago), licensed MIT. It adds 134 tokens to every session and 2,138 once invoked, about $0.0007 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.
Other skills, from other repositories
math-unicode
Use whenever you need to express mathematical notation — equations, filters, set-builder, statistics, calculus, logic, ratios, drops, counts. Emit Unicode math glyphs INLINE; never wrap in $…$, \(...\), or $$...$$. Terminal coding agents (Claude Code, Codex CLI, and others) do not render LaTeX, so raw delimiters…
sdd-serve
Serve the SDD Builder's AI request queue: claim requests with sddnextrequest, draft the proposal, answer with sddrespondrequest. Never writes spec files — the user accepts each proposal in the builder. Use when the user asks to attend, serve or listen to the SDD board queue. / Atiende la cola de peticiones del SDD…
sdd-workflow
Guide a project with Spec-Driven Development (SDD) discipline - idea, approved spec, consistent plan, tasks, a gate that verifies approval and consent, implementation, validation, and logbook. Bilingual EN/ES. Use when the user wants to start, spec, plan, implement, or validate work with SDD, or mentions specs, plans…
eo-brainstorming
对不成形的想法做发散、对抗、拆解和方向决策。触发:帮我想想 / 头脑风暴 / brainstorming / /eo-brainstorming。 NOT FOR: 普通技术讨论或具体实现问题(只在用户明确"想想方向"时触发)。.
eo-change-review
对 change.md 做方案级审查(Delta 正确性、TODO 完整性、AC 覆盖)。触发:审查 change / change 审查 / 审方案 / /eo-change-review。 NOT FOR: 代码审查(/eo-review)、spec 审查(/eo-spec-review)、implement 内的回归审查。.
eo-miniapp-ideation
微信小程序需求挖掘与 MVP 构思,含变现模型和流量路径前置思考。触发:帮我想个小程序 / 小程序选品 / 小程序方向 / /eo-miniapp-ideation。 NOT FOR: 开发 / 备案 / 审核等执行流程。.