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 agentmods add skills/alchemiststudiosdotai/harness-engineering/harness-mapnpx skills add alchemiststudiosDOTai/harness-engineering --skill harness-mapgit clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineeringWrote 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/alchemiststudiosdotai/harness-engineering/harness-map)<a href="https://agentmods.dev/skills/alchemiststudiosdotai/harness-engineering/harness-map"><img src="https://agentmods.dev/badge/skills/alchemiststudiosdotai/harness-engineering/harness-map.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.01659 |
| Opus 5 | $0.00028 | $0.00830 |
| Sonnet 5 | $0.00011 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
harness-map 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Map
Map the repository's actual harness: the mechanical checks, policies, workflows, and artifacts that make change safe.
This skill is narrower than generic codebase research. It is specifically for answering questions like:
- "What is the harness in this repo?"
- "What does
checkactually run?" - "Which layers are local vs CI vs docs vs evidence?"
- "How is architecture enforced here?"
- "What operator surfaces teach agents how to use the harness?"
Core Principle
Map the harness as implemented, not as imagined.
Prefer:
- commands that actually run
- config files that actually enforce policy
- CI workflows that actually gate merges
- docs and playbooks that actually structure investigations
- agent/operator files that actually expose the workflow
Avoid:
- aspirational architecture prose without enforcement
- recommendations before the map exists
- broad codebase summaries that skip the gate structure
What Counts as Harness
A repo harness usually includes some or all of these layers:
- Canonical local command
just check,make check,task check,npm test, etc.
- Architecture boundaries
- Import Linter, dependency-cruiser, Bazel visibility, custom dependency tests
- Structural rules
- ast-grep, semgrep, custom lint rules, codemod rule tests
- Behavioral verification
- unit/integration tests, snapshots, goldens, deterministic checks, build verification
- Docs ratchets
- docs link checks, nav checks, metadata/frontmatter checks, allowlists
- CI decomposition
- matrix jobs or separate workflows that mirror harness gates
- Evidence workflows
- session logs, diff reports, chunk docs, experiment records, replay/debug artifacts
- Operator surface
AGENTS.md,.codex/, environment files, repo-local skills, slash commands
When to Use
Use this skill when the user asks to:
- map or explain the harness
- identify all gate layers in a repo
- compare local checks with CI checks
- document how architectural constraints are enforced
- understand how agents/operators are expected to use the repo safely
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.
- 4d ago First seen · 280 lines · 55 tokens per session scan A ace13f13fd77
harness-map is a skill published in the GitHub repository alchemiststudiosDOTai/harness-engineering (104 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,659 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…