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/jpm1118/threadwork/finishingnpx skills add JPM1118/Threadwork --skill finishinggit clone --depth 1 https://github.com/JPM1118/ThreadworkWhat 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 | $0.00000 | $0.01327 |
| Opus 5 | $0.00000 | $0.00664 |
| Sonnet 5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
finishing 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finishing Skill
Assess feature completeness and determine the appropriate landing strategy (merge directly or create PR).
When to Use This Skill
Use this skill when:
- All tasks in an epic are complete
- Code review has passed
- You're ready to land the feature
Prerequisites
- All tasks in the epic are closed
- All tests pass
- Code review complete (or not required)
- You're in the feature worktree/branch
Skill Workflow
Step 1: Verify Epic Completeness
# Check epic status
bd --no-daemon show {epic-id} --children
Verify:
- All tasks are closed
- No tasks are blocked or in-progress
- Epic description matches what was built
Step 2: Run Final Verification
# Run full test suite
npm test
# Run build (if applicable)
npm run build
# Run linter (if applicable)
npm run lint
All checks must pass before proceeding.
Step 3: Check Git Status
# Ensure all changes are committed
git status
# Check branch is up to date with remote
git fetch origin
git log origin/{base_branch}..HEAD --oneline
If there are uncommitted changes:
- Commit them with appropriate message
- Or stash if they shouldn't be included
Step 4: Assess Landing Strategy
Decision factors:
| Factor | Merge Directly | Create PR |
|---|---|---|
| Protected branch | No | Yes |
| Team review required | No | Yes |
| CI/CD pipeline | Optional | Required |
| Solo developer | Usually | Sometimes |
| Risky changes | No | Yes |
Read project configuration:
cat .threadwork.yaml
Check base_branch - if it's a protected branch (main, dev, uat), a PR is likely required.
Step 5: Execute Landing Strategy
Based on assessment, invoke the appropriate action:
Option A: Direct Merge (if allowed)
Use when:
- Base branch is not protected
- No PR required by workflow
- All checks pass locally
Invoke /finish-and-close command:
/finish-and-close --epic {epic-id} --strategy merge
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.
- 2d ago First seen · 231 lines · 0 tokens per session scan A 3637284d6d30
finishing is a skill published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,327 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.