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 jason21wc/ai-governance-mcp --skill completion-sequencegit clone --depth 1 https://github.com/jason21wc/ai-governance-mcpWrote 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/jason21wc/ai-governance-mcp/completion-sequence)<a href="https://agentmods.dev/skills/jason21wc/ai-governance-mcp/completion-sequence"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/completion-sequence/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/jason21wc/ai-governance-mcp/completion-sequence"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/completion-sequence.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.00054 | $0.00506 |
| Opus 5.5 | $0.00022 | $0.00202 |
| Sonnet 5.5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
completion-sequence 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 1mo 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
Completion Sequence
Read checklist.md completely and apply the sections matching the actual change.
Its Continue or hand off rule separates per-change validation and durable checkpoints
from ending the authorized task. Continue remaining work after a checkpoint; do not
turn a progress update into a request to proceed.
For a completed topic worktree, use integrate.sh; it makes the default branch
explicit and distinguishes a concurrent publish race (exit 3) from other failures.
The load-bearing order (design of record: ADR-31, which carries the scratch-repo evidence for why this ordering and not another) is:
commit implementation -> refresh live origin default -> integrate -> retest
-> write closeout memory on that base -> commit -> publish exact topic HEAD
-> run the internal full check -> fast-forward default -> retry if origin moved
Do not write the final shared-memory snapshot before refresh, do not merge a
possibly stale local default branch, and do not force-push the integration branch.
The helper is optimistic: it detects and repeats after a sibling wins the race
instead of serializing all sessions behind a global lock.
Where the repository declares the local publication gate, direct default-branch
pushes are blocked and the helper supplies a one-shot exact-HEAD token only after
the repository's internal full check passes without moving HEAD or dirtying the
tree, and its structured record reports zero failed or unavailable checks. GitHub
checks are optional clean-runner evidence, not publication authority.
Repositories with scripts/pre_push.py additionally require an explicitly installed
raw hook and accepted exact-scope review records before the full check. See the
repository's docs/publication-evidence.md for request/report retention. Topic
checkpoints can remain unfinished; a checkpoint does not renew user permission.
A client hook can still be bypassed deliberately with --no-verify. The raw hook
checks every tuple for its obligations; its pre-commit delegate still exposes only
the first eligible ref to delegated checks. Older installations have only that
legacy boundary. The helper uses one-ref pushes. These are cooperative local
controls, not server-side protection.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +5 lines c9628ed778ff
- 1mo ago Changed · +13 lines 26b202341e7a
- 2mo ago First seen · 23 lines · 54 tokens per session scan A 5224018654cb
completion-sequence is a skill published in the GitHub repository jason21wc/ai-governance-mcp (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 54 tokens to every session and 506 once invoked, about $0.0002 per session on Opus 5.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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.