test-harness

A prompt-testing tool for checking an agent-review prompt or test fixture during development.

In plain words
What is it for?
Use it to run the agent-review harness in an iterative development loop against a rule or fixture.
Why use it?
It gives quick, low-detail feedback while you refine prompts, before running the slower reliability check used before release.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/getlien/lien/test-harness
Any agent
npx skills add getlien/lien --skill test-harness
Clone the repo
git clone --depth 1 https://github.com/getlien/lien

Made for: Claude Code, Codex.

Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,065 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00082 $0.02065
Opus 5 $0.00041 $0.01033
Sonnet 5 $0.00016 $0.00413
Haiku 4.5 $0.00008 $0.00206

Measured 2d ago against content hash d825b78223d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-harness 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.

.claude/skills/test-harness/SKILL.md · 161 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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.

  1. 2d ago First seen · 161 lines · 82 tokens per session scan A d825b78223d8

Subscribe to this mod's changes

test-harness is a skill published in the GitHub repository getlien/lien (2 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 82 tokens to every session and 2,065 once invoked, about $0.0004 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-08-31.

Related

Other skills, from other repositories

lilbee-mcp

Search and manage the user's local lilbee knowledge base over MCP. Use whenever the user has indexed code, docs, PDFs, or web pages into lilbee and you need cited answers, or whenever they ask you to ingest content, swap models, or tune retrieval against their library. Every fact returned cites file and line.…

tobocop2/lilbee · 95 tokens

lilbee-mcp-wiki

Wiki layer for lilbee. Use only when the user explicitly asks about wiki / concept / entity / synthesis pages, or when lilbeestatus shows a built wiki. Requires the lilbee-mcp skill to be active for the underlying MCP connection.

tobocop2/lilbee · 60 tokens

handoff

Prepare a concise repository-work handoff and write it only after explicit confirmation to the visible repository-root Markdown file MEMENTOHANDOFF.md. Use when the user asks to capture, save, or pass current work to a later session or collaborator; never perform hidden or automatic writes.

caiowilson/MCP-memento · 59 tokens

prime

Orient to an unfamiliar or resumed repository through bounded reads of repo instructions, root manifests, Git state, and a few high-signal files. Use when the user asks to prime, orient to, understand, or resume work in a repository; do not use for semantic search or background indexing.

caiowilson/MCP-memento · 60 tokens

review-changes

Review current staged, unstaged, and untracked Git changes for correctness and regression risk, grounded in changed paths, diffs, focused file reads, and nearby test discovery. Use when the user asks to review local changes or a working-tree diff; do not use for broad repository audits.

caiowilson/MCP-memento · 62 tokens

enzyme-sqlite-source

Connect an unfamiliar SQLite database to Enzyme without changing the source data. Inspect the database, decide which query columns represent identity, people, time, content, and folders, show real examples for approval, save the mapping in TOML, and verify init and refresh. Use for email, message, CRM, archive, or…

byenzyme/enzyme · 80 tokens