test-harness

Solid

Install vigiles and test a Claude Code harness — hooks, skills, settings, CLAUDE.md — by picking the right tier (unit / deterministic / eval) and writing a test that passes. Use when the user wants to check that a hook fires or blocks, that a skill triggers, that injected context lands, or that a harness change moves what the agent does.

AI & Automation 13 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
38
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

Test the Claude Code **harness** — the hooks, skills, settings, and CLAUDE.md that steer an agent — as the assembled machine it ships as. vigiles gives three tiers, cheapest first; this skill picks the right one, writes the test, and runs it. The guiding rule: **start at the cheapest tier that can answer the question, and climb only when it genuinely can't.** Two of the three tiers need no model and no API key, so they run on every commit for free — reach for the paid real-model tier only when the question actually requires a real model. ## Step 0 — Pick the tier (the judgment call) Match what you're testing to the cheapest tier that can answer it: | What you're testing | Tier | Cost | API | | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------------------------------------------ | --------------------------------------------------------------------------------------------- | | "Does this hook block/allow event X?" — pure hook logic, **every** event type (incl. Edit/Write, PreCompact, SessionEnd, SubagentStop) | **Unit** | free, milliseconds, no `claude` | `runHook` ...

Details

Author
zernie
Repository
zernie/vigiles
Created
4 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

harness-health-audit

Audit the health of an AI-coding harness — the CLAUDE.md / AGENTS.md files, rules, skills, agents, hooks, and commands that steer an agent in a repository — across four questions a linter cannot answer: is it TRUE (does it match the real code?), is it USED (do skills actually trigger and does the loop actually verify?), is it AFFORDABLE (is it inside the budget where instructions are still followed?), and is it SAFE (is a live, accurate instruction still a good idea — permission bypasses, unpinned remote scripts, untrusted content flowing in as instructions? — safety findings are flagged for the user's decision, never auto-removed). Then surgically correct or remove only what is proven wrong or dead. Use whenever the steering layer may have rotted or may not be working: "하네스 점검해줘", "하네스 드리프트 감사", "CLAUDE.md가 실제랑 맞는지 봐줘", "룰/스킬이 최신인지 확인해줘", "스킬이 제대로 활용되는지 봐줘", "루프 엔지니어링 잘 되고 있는지 검토해줘", "죽은 훅/커맨드 정리해줘", "하네스 안전한지 점검해줘", "audit my harness", "check the rules still match the real stack", "are my skills actually be

3 Updated today
uzysjung
AI & Automation Listed

bootstrap-harness

Create a complete AI-agent harness (CLAUDE.md + supporting docs system) for any project. Portable across Python/Java/TS/Go. Based on 2025-2026 best practices (AGENTS.md spec, GitHub's 2,500-repo study, ACE paper, context-engineering research). Use when a repo has no harness, was just cloned/scaffolded, or its docs are bloated/stale and need a structured rebuild.

3 Updated 1 weeks ago
TIANTIAN-ZHAN
AI & Automation Listed

harness-eng

Use when designing, evaluating, or simplifying an agent project harness: AGENTS.md/CLAUDE.md rules, startup scripts, progress logs, feature trackers, handoffs, evaluator rubrics, quality documents, repo-local knowledge maps, and mechanical guardrails for coding agents. Especially useful when converting raw agent-workflow notes into a concise, verifiable project control layer.

3 Updated yesterday
MasihMoafi