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/zahardev/aicontext/finish-tasknpx skills add zahardev/aicontext --skill finish-taskgit clone --depth 1 https://github.com/zahardev/aicontextWrote 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/zahardev/aicontext/finish-task)<a href="https://agentmods.dev/skills/zahardev/aicontext/finish-task"><img src="https://agentmods.dev/badge/skills/zahardev/aicontext/finish-task.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.1 | $0.00037 | $0.00057 |
| Opus 5 | $0.00018 | $0.00028 |
| Sonnet 5 | $0.00007 | $0.00011 |
| Haiku 4.5 | $0.00004 | $0.00006 |
Grade A, and why
finish-task 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 5d 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
Read and follow .aicontext/prompts/finish-task.md
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.
- 5d ago First seen · 7 lines · 37 tokens per session scan A 261105d52d72
finish-task is a skill published in the GitHub repository zahardev/aicontext (2 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 57 once invoked, about $0.0002 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
ship
Ship workflow: merge main, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
pr-all-in-one
Unified commit and PR workflow. Auto-commits changes, creates/updates PRs with smart issue linking and multi-language support.
ship
Run local CI checks and ship changes — create branch, commit, push, and PR. Optionally link to a GitHub issue. Use --full to run all workspace checks. Use when changes are ready to ship.
ship
Commit and push the current work properly — lint, run the release gate, write a detailed commit message, push to GitHub. Use whenever work reaches a milestone or the user says ship it, commit, or push.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…