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 cckyros/goal-acceptance --skill amend-acceptance-criteriagit clone --depth 1 https://github.com/cckyros/goal-acceptanceWrote 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/cckyros/goal-acceptance/amend-acceptance-criteria)<a href="https://agentmods.dev/skills/cckyros/goal-acceptance/amend-acceptance-criteria"><img src="https://agentmods.dev/badge/skills/cckyros/goal-acceptance/amend-acceptance-criteria/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cckyros/goal-acceptance/amend-acceptance-criteria"><img src="https://agentmods.dev/badge/skills/cckyros/goal-acceptance/amend-acceptance-criteria.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00128 |
| Opus 5 | $0.00009 | $0.00064 |
| Sonnet 5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
amend-acceptance-criteria 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 11d 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.
What it actually says
When requirements expand during execution, call this skill to add new criteria. Existing criteria are not modified — only new ones are appended. A human-readable reason is required to record why the amendment was made.
Amended criteria are marked with addedAfterLock: true in the returned
criteria list.
Example:
- criteria:
- id: perf-check description: Response time under 200ms required: true method: test
- reason: Performance requirement added after initial scope discussion
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.
- 11d ago First seen · 21 lines · 17 tokens per session scan A e5a6e3a59add
amend-acceptance-criteria is a skill published in the GitHub repository cckyros/goal-acceptance (3 stars, last pushed 14d ago), licensed MIT. It adds 17 tokens to every session and 128 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.
Other skills, from other repositories
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
yao-board
Kanban board and task query expert. ALWAYS invoke this skill when the user asks about boards, tasks, task status, or project progress. Do not guess task state — use this skill first.
linear-issue-delivery
Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
notion-databases
Query and update Notion databases with explicit database identity, property-aware inputs, bounded reads, and confirmation before material writes.
linear-project-updates
Produce concise Linear project updates from current milestones, completed and blocked issues, delivery risks, and next actions.
linear-sprint-planning
Build a realistic Linear cycle plan from current priorities, dependencies, estimates, carryover, and team capacity without silently rescheduling work.