Borrowing it
Nothing to install: this file belongs to aiblueprinthq/ai-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aiblueprinthq/ai-blueprint/main/.agents/skills/complete/SKILL.mdgit clone --depth 1 https://github.com/aiblueprinthq/ai-blueprintWrote 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/aiblueprinthq/ai-blueprint/complete)<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/complete"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/complete/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/aiblueprinthq/ai-blueprint/complete"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/complete.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.04624 |
| Opus 5 | $0.00028 | $0.02312 |
| Sonnet 5 | $0.00011 | $0.00925 |
| Haiku 4.5 | $0.00006 | $0.00462 |
Grade A, and why
complete 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 today.
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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
complete - log the finished work, make the work commit, and merge
Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
First action: Before project inspection, preflight, or any other tool call,
publish running to blueprint/.state/run.json using the dashboard activity
contract in AGENTS.md.
Where this sits in the workflow:
/feature, /fix, or /rollback -> /implement -> [complete] -> next
(the spec) (build it) (commit + merge + log)
/implement built the feature, fix, or rollback on its branch, with optional per-step commit
checkpoints. This skill closes it out: it logs the work, makes the single
work-level commit, and squash-merges. Run it only when the work is done,
reviewed, and the documented Verify command, or the fallback build and tests,
passes.
Before you start
Read blueprint/config.json. A missing file means the built-in defaults apply.
If the file exists but is invalid, stop and point the user to /doctor.
Configuration can strengthen or shape the completion gates, but it never grants
permission to commit, merge, push, deploy, publish, or take destructive action.
Before requiring a real active spec, check for pending completion using
reference/completion-recovery.md. A matching archive may mean archival was
interrupted, the work commit awaits merge, or the merge already finished. Follow
that phase instead of restarting logging. Missing or ambiguous evidence stops
with concrete recovery steps; a reset stub never authorizes selecting new work.
Recovery uses archive and Git proof, never dashboard activity as authority.
For a normal completion with no recovery in progress, continue below.
Confirm the work is actually finished: blueprint/context/current-feature.md
holds a real spec, its steps are built on a branch, and Verify, or the fallback
build and tests, passes. Apply the configured regular quality gates below before
logging or committing. Uncommitted step work is expected because per-step
checkpoints are optional; this skill commits it. Don't require the steps to be
pre-committed.
What ships with it
1 file 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.
- today Changed · +48 lines 011e195ac0e2
- 2d ago Changed · +28 lines 782a68c2d248
- 5d ago Changed · +4 lines c8df67604f92
- 6d ago Changed · +53 lines · -70 tokens per session 0f5470d30cbd
- 10d ago First seen · 228 lines · 127 tokens per session scan A 833c5a07ca8a
complete is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (384 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 4,624 once invoked, about $0.0003 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-30.
Other skills, from other repositories
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
gsd-pause-work
Create context handoff when pausing work mid-phase.
gsd-ship
Create PR, run review, and prepare for merge after verification passes.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.