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 skills add kidow/skills --skill setup-harnessgit clone --depth 1 https://github.com/kidow/skillsWrote 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/skills/kidow/skills/setup-harness)<a href="https://agentmods.dev/skills/kidow/skills/setup-harness"><img src="https://agentmods.dev/badge/skills/kidow/skills/setup-harness/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/skills/kidow/skills/setup-harness"><img src="https://agentmods.dev/badge/skills/kidow/skills/setup-harness.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.00166 | $0.01041 |
| Opus 5.5 | $0.00066 | $0.00416 |
| Sonnet 5.5 | $0.00033 | $0.00208 |
| Haiku 4.5 | $0.00017 | $0.00104 |
Grade D, and why
setup-harness scanned grade D with 3 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. `permissions.deny`: `rm -rf *`, `curl *`, `wget *`, `sudo *`, `chmod 777 *`, `git push --force *`, `Read(.env*)`, `Read(**/secrets/**)`. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
3. `permissions.deny`: `rm -rf *`, `curl *`, `wget *`, `sudo *`, `chmod 777 *`, `git push --force *`, `Read(.env*)`, `Read(**/secrets/**)`. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. `permissions.deny`: `rm -rf *`, `curl *`, `wget *`, `sudo *`, `chmod 777 *`, `git push --force *`, `Read(.env*)`, `Read(**/secrets/**)`. How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Engineering Setup
Build harness in 3 stages, ordered by impact. Stop after any stage if user is satisfied — each delivers value standalone. See REFERENCE.md for theory.
Stage 1 — Inform (AGENTS.md + CLAUDE.md stub)
- Detect project stack from
package.json,Cargo.toml,pyproject.toml,go.mod. - Draft
AGENTS.md(≤ 60 lines) using templates/AGENTS.md. Pre-fill Project Stack only. - Mark Forbidden and Past Failures as
# DRAFT — review required. - Write
CLAUDE.mdcontaining one line:@AGENTS.md(Claude Code import directive). - Show diff. Require explicit confirmation before save.
- Warn: "ETH Zurich research: LLM-generated AGENTS.md drops agent performance 3% and raises cost 20%. Past Failures must come from real incidents — leave empty if none."
Pnpm is the standard. AGENTS.md fixes Package manager: pnpm. Refuse to set otherwise.
Stage 2 — Constrain (permissions)
- Create
.claude/settings.jsonfrom templates/settings.json. permissions.allow: read/edit/write/test/git basics.permissions.deny:rm -rf *,curl *,wget *,sudo *,chmod 777 *,git push --force *,Read(.env*),Read(**/secrets/**).- No
PreToolUsehooks.permissions.denyis the single defense layer for dangerous commands.
Stage 3 — Verify (Stop hook required, CI optional)
Pick one variant from templates/settings.json:
- lite (default): Stop hook runs
pnpm lintonce at session end. - strict: Stop hook runs
pnpm lint && pnpm typecheck && pnpm test --run.
Never use PostToolUse to run tests/typecheck — runs on every edit, kills throughput.
Optional: Scaffold .github/workflows/agent-pr-checks.yml from templates/agent-pr-checks.yml. Hooks give immediate feedback per session. CI is the merge gate.
Correct (no extra files)
Failure handling lives inside AGENTS.md Past Failures and the workflow rule:
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 70 lines · 166 tokens per session scan D 86890e54d609
setup-harness is a skill published in the GitHub repository kidow/skills (2 stars, last pushed 21d ago), licensed MIT. It adds 166 tokens to every session and 1,041 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…