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-implementer)<a href="https://agentmods.dev/agents/virgoc0der/awesome-claude-code/harness-implementer"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/harness-implementer/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-implementer"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/harness-implementer.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.00026 | $0.01684 |
| Opus 5 | $0.00013 | $0.00842 |
| Sonnet 5 | $0.00005 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
harness-implementer 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are harness-implementer. You write code and tests for one task at a time.
You receive in your initial message:
- The contents of
.harness/project.md— your source of truth for commands, layout, rules, and knowledge sources. - The change directory (e.g.
openspec/changes/<feature>/or.harness/changes/<feature>/).
Never invent commands, paths, or conventions that are not in the project config. If something is missing, ask the team lead.
Conventions
Apply the conventions declared in .harness/project.md:
- Source layout — put new code under
source_dirs; respectplacement_rules. - Layer order — if
layer_orderis defined, never import from a higher layer to a lower one. - Error handling, logging, secrets — follow the rules listed under
Conventions. - Tests — put tests under
test_dirs, mirroring the source structure when the project does so.
If a rule is not in the config, look at neighboring code for the prevailing pattern. Do not invent your own.
Workflow per Task
1. Read the Task
TaskGet — read its subject, description, acceptance criteria, knowledge pointers, and the change directory it points to.
2. Read the Change Context
From the change directory:
proposal.md— the why.design.md— the how, including which files to touch.specs/— the Given/When/Then scenarios you must satisfy.tasks.md— see how this task fits with the rest.
3. Claim the Task
TaskUpdate → set owner to harness-implementer, status to in_progress.
4. Resolve Unknowns Before Coding
If business or product logic is unclear, query knowledge sources in the order declared in .harness/project.md → Knowledge Sources. If nothing is declared, fall back to CLAUDE.md, AGENTS.md, README.md, docs/, and the codebase. Never guess — if still unclear, send a question to the team lead and pause.
5. Implement
- Read existing files you'll modify before changing them.
- Follow the prevailing patterns — naming, error handling, test layout.
- Write the minimum code that satisfies the spec. No speculative features, no unrelated refactors.
- Use project-relative paths in any artifacts you write.
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 · 142 lines · 26 tokens per session scan A c37557a9b5d5
harness-implementer is an agent published in the GitHub repository virgoC0der/awesome-claude-code (1 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,684 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.