What is trellis-finish-work?

A pre-commit checklist for Trellis projects, used after code is written and tested. It checks code quality, tests, type checking, and whether project specification documents match the code.

Use it to run linting, type checks, and tests, review common code issues, and update backend, frontend, or guide specifications when needed.

It helps catch unfinished work and undocumented changes before submitting or committing code.

How lie5860/openai-search-mcp configures Claude Code and Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to lie5860/openai-search-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/lie5860/openai-search-mcp/main/.cursor/commands/trellis-finish-work.md

Clone the repo

git clone --depth 1 https://github.com/lie5860/openai-search-mcp

Made for: Claude Code, Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lie5860/openai-search-mcp/trellis-finish-work/github.svg)](https://agentmods.dev/commands/lie5860/openai-search-mcp/trellis-finish-work)

Your own site

<a href="https://agentmods.dev/commands/lie5860/openai-search-mcp/trellis-finish-work"><img src="https://agentmods.dev/badge/commands/lie5860/openai-search-mcp/trellis-finish-work/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lie5860/openai-search-mcp/trellis-finish-work"><img src="https://agentmods.dev/badge/commands/lie5860/openai-search-mcp/trellis-finish-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 918 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 86% copy Near-identical to another mod in the catalogue.

Token cost

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.00000	$0.00918
Opus 5	$0.00000	$0.00459
Sonnet 5	$0.00000	$0.00184
Haiku 4.5	$0.00000	$0.00092

Measured 11d ago against content hash 582e968ada1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

trellis-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 11d 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.

Origin

This is a copy

86% identical to finish-work — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/commands/trellis-finish-work.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 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 lint passes with 0 errors?
pnpm type-check passes with no type errors?
Tests pass?
No console.log statements (use logger)?
No non-null assertions (the x! operator)?
No any types?

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: If infra/cross-layer changed but the related spec is still abstract, do NOT finish. Run /trellis-update-spec manually first.

3. API Changes

If you modified API endpoints:

Input schema updated?
Output schema updated?
API documentation updated?
Client code updated to match?

4. Database Changes

If you modified database schema:

Migration file created?
Schema file updated?
Related queries updated?
Seed data updated (if applicable)?

5. Cross-Layer Verification

Read the full file on GitHub · 144 lines

Changes

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.

11d ago First seen · 144 lines · 0 tokens per session scan A 582e968ada1b

Subscribe to this mod's changes

trellis-finish-work is a command published in the GitHub repository lie5860/openai-search-mcp (13 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 918 tokens. A static security scan graded it A with 0 findings. It is 86% identical to finish-work, differing in 22 lines, and is treated as a copy.

Git and workflow

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

handoff

Export a Waybill Bundle by default, or import one when requested.

wardmos/waybill · 13 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

openai-search-mcp: Command for Claude Code