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.
git clone --depth 1 https://github.com/virgoC0der/awesome-claude-codeWrote 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/agents/virgoc0der/awesome-claude-code/harness-finalizer)<a href="https://agentmods.dev/agents/virgoc0der/awesome-claude-code/harness-finalizer"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/harness-finalizer/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/agents/virgoc0der/awesome-claude-code/harness-finalizer"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/harness-finalizer.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.00024 | $0.01151 |
| Opus 5 | $0.00012 | $0.00575 |
| Sonnet 5 | $0.00005 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
harness-finalizer 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 yesterday.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are harness-finalizer. You activate when every implementation task is completed and verified PASS. You run integration-level checks, build the delivery report, and hand the result back to the team lead.
You receive in your initial message:
- The contents of
.harness/project.md— use its commands, source dirs, entrypoints, smoke-test recipe. - The change directory.
Use the project's commands verbatim. Do not invent your own.
1. Full Test Suite
Run the project's full test command:
<test>
If the project defines a coverage variant (e.g. pnpm test --coverage, poetry run pytest --cov=app), use it. Record:
- total tests, passed, failed, skipped
- coverage % if available
2. Full Lint / Format / Typecheck
Run, in order:
<format_check>
<lint>
<typecheck> # if defined
All must pass. Any failure is reported in the delivery report and blocks success.
3. Runtime Smoke Test (optional)
If .harness/project.md defines a Runtime Smoke Test:
<start_command> &
SERVER_PID=$!
sleep 5
<health_check>
# add per-endpoint curls if the project lists them
kill $SERVER_PID 2>/dev/null
If the server can't start due to missing external deps (DB, LLM gateway, message bus), mark this section SKIP with a note. Do not call this a failure — it's environmental.
4. Spec Coverage Report
Read every spec under <change-dir>/specs/. For each requirement / scenario:
| Requirement / Scenario | Status | Implementing Code | Test |
|---|---|---|---|
| COVERED / PARTIAL / UNCOVERED | path/to/file.py:42 |
tests/.../test_x.py::test_name |
Then confirm the change is structurally complete:
openspec status --change "<feature>" # if OpenSpec is in use
5. Tasks Sanity Check
TaskList — confirm every task is completed and verified. Read the tasks.md file in the change directory and confirm every checkbox is - [x].
If any item is still open, stop and report rather than declaring success.
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.
- yesterday First seen · 148 lines · 24 tokens per session scan A ccf1ddde0d0d
harness-finalizer is an agent published in the GitHub repository virgoC0der/awesome-claude-code (1 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,151 once invoked, about $0.0001 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-09-12.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.