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 commands/mistydew/tokenicode-deepseek-alpha/finish-workgit clone --depth 1 https://github.com/mistydew/tokenicode-deepseek-alphaWrote 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/commands/mistydew/tokenicode-deepseek-alpha/finish-work)<a href="https://agentmods.dev/commands/mistydew/tokenicode-deepseek-alpha/finish-work"><img src="https://agentmods.dev/badge/commands/mistydew/tokenicode-deepseek-alpha/finish-work.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 | $0.00000 | $0.01027 |
| Opus 5 | $0.00000 | $0.00513 |
| Sonnet 5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
finish-work 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- finish-work — 100% identical, 0 lines differ
- finish-work — 100% identical, 0 lines differ
- finish-work — 100% identical, 0 lines differ
- finish-work — 100% identical, 0 lines differ
- trellis-finish-work — 86% identical, 22 lines differ
- trellis-finish-work — 86% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finish Work - Pre-Commit Checklist
Before submitting or committing, use this checklist to ensure work completeness.
Timing: After code is written and tested, before commit
Checklist
1. Code Quality
# Must pass
pnpm lint
pnpm type-check
pnpm test
-
pnpm lintpasses with 0 errors? -
pnpm type-checkpasses with no type errors? - Tests pass?
- No
console.logstatements (use logger)? - No non-null assertions (the
x!operator)? - No
anytypes?
1.5. Test Coverage
Check if your change needs new or updated tests (see .trellis/spec/unit-test/conventions.md):
- New pure function → unit test added?
- Bug fix → regression test added in
test/regression.test.ts? - Changed init/update behavior → integration test added/updated?
- No logic change (text/data only) → no test needed
2. Code-Spec Sync
Code-Spec Docs:
- Does
.trellis/spec/backend/need updates?- New patterns, new modules, new conventions
- Does
.trellis/spec/frontend/need updates?- New components, new hooks, new patterns
- Does
.trellis/spec/guides/need updates?- New cross-layer flows, lessons from bugs
Key Question:
"If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"
If YES -> Update the relevant code-spec doc.
2.5. Code-Spec Hard Block (Infra/Cross-Layer)
If this change touches infra or cross-layer contracts, this is a blocking checklist:
- Spec content is executable (real signatures/contracts), not principle-only text
- Includes file path + command/API name + payload field names
- Includes validation and error matrix
- Includes Good/Base/Bad cases
- Includes required tests and assertion points
Block Rule:
In pipeline mode, the finish agent will automatically detect and execute spec updates when gaps are found.
If running this checklist manually, ensure spec sync is complete before committing — run /trellis:update-spec if needed.
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 · 154 lines · 0 tokens per session scan A cc92cad9e94c
finish-work is a command published in the GitHub repository mistydew/tokenicode-deepseek-alpha (367 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,027 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-30.
Other commands, from other repositories
write-tests
Generate comprehensive test coverage for existing code.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test
Generate comprehensive tests.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
unit-test
Write / run the unit tests for the feature. (AIDLC Unit Test phase) Usage: /unit-test.