Borrowing it
Nothing to install: this file belongs to zywkloo/wtcraft. 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/zywkloo/wtcraft/main/.agents/skills/finishwt/SKILL.mdgit clone --depth 1 https://github.com/zywkloo/wtcraftWrote 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/zywkloo/wtcraft/finishwt)<a href="https://agentmods.dev/skills/zywkloo/wtcraft/finishwt"><img src="https://agentmods.dev/badge/skills/zywkloo/wtcraft/finishwt/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/zywkloo/wtcraft/finishwt"><img src="https://agentmods.dev/badge/skills/zywkloo/wtcraft/finishwt.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.00036 | $0.00149 |
| Opus 5.5 | $0.00014 | $0.00060 |
| Sonnet 5.5 | $0.00007 | $0.00030 |
| Haiku 4.5 | $0.00004 | $0.00015 |
Grade A, and why
finishwt 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
Finish a wtcraft worktree task
Read:
.agent-harness/finisher.mdworktrees/<name>/.worktree-task.mdfor the target worktree
Run the task's declared verification, check the changeset against Scope and
Off-limits, and report results. Then run the re-plan checkpoint from
finisher.md: challenge the task's premises (especially Scope, Off-limits, and
the task boundary) and get explicit user confirmation before any push or PR.
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 First seen · 17 lines · 36 tokens per session scan A 70972d1016ab
finishwt is a skill published in the GitHub repository zywkloo/wtcraft (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 149 once invoked, about $0.0001 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-09-11.
Other skills, from other repositories
comet-github-pr-review
A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.
issue-work-loop
Run Herdr loops for one open GitHub issue (resolve→review→fix) or an existing PR (review→lazy fixer) until CLEAN. Don't use for plain resolution without review, review-only/no-fix requests, backlog automation, or merging.
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
pr-review
PR self-review — review changes, produce checklist, update rules.
gh-address-comments
Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging…
doris-repo-review
Review an Apache Doris PR from a local clone with the same multi-agent, shared-ledger convergence workflow as the CI Code Review Runner. Use when the user supplies a PR to /doris-repo-review, asks to review a Doris PR locally, or asks for the CI-style review flow. Safely align only the current worktree to the exact PR…