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 ashutoshsinghpr7/wikiskill --skill trace-harness-launch-failuregit clone --depth 1 https://github.com/ashutoshsinghpr7/wikiskillWrote 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/ashutoshsinghpr7/wikiskill/trace-harness-launch-failure)<a href="https://agentmods.dev/skills/ashutoshsinghpr7/wikiskill/trace-harness-launch-failure"><img src="https://agentmods.dev/badge/skills/ashutoshsinghpr7/wikiskill/trace-harness-launch-failure/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/ashutoshsinghpr7/wikiskill/trace-harness-launch-failure"><img src="https://agentmods.dev/badge/skills/ashutoshsinghpr7/wikiskill/trace-harness-launch-failure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00420 |
| Opus 5 | $0.00015 | $0.00210 |
| Sonnet 5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
trace-harness-launch-failure 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 3d 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.
What it actually says
Trace Harness Launch Failure — empty sessions, scores from deliverables
Problem
Four training traces contain ONLY the initial task prompt: 1 message,
0 tool calls, 0 API calls, ~1 s duration. No agent reasoning, tool call, or
final answer anywhere — yet meta.json carries scores (0.0 / 1.0).
Root cause
Every recorded run died at launch: runs/<task>/stdout.txt shows
"HTTP 400: default is not a valid model ID" — the harness sent an invalid
model ID instead of the configured model, so the agent never executed. The
scores were produced by grading the on-disk deliverables against the
exact-match graders in tasks.json — not from any recorded agent behavior.
Fix
- Before analyzing "agent behavior", verify the session actually ran: check
api_call_count/tool_call_count/message_countin the trace and stdout.txt for launch errors. Empty trace == no behavioral evidence. - When traces are empty, reconstruct ground truth by diffing the on-disk
deliverable against the task's grader expectation
(
tasks.json→grader.expected), and read spec.md + input data to explain the score. - Treat prior-iteration behavioral claims as unverifiable until new traces confirm them; flag evidence status in the run log.
- Surface the harness bug so the runner is fixed before the next iteration, otherwise every proposal rests on inferred data.
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.
- 3d ago First seen · 42 lines · 31 tokens per session scan A 95b06112310e
trace-harness-launch-failure is a skill published in the GitHub repository ashutoshsinghpr7/wikiskill (133 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 420 once invoked, about $0.0002 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-05.
Other skills, from other repositories
harness-optimizer
Optimize an AI agent's harness for MCP-Atlas benchmark. Use when analyzing execution traces, diagnosing failures, and proposing improved prompts, skills, or harness code.
debug-and-fix
Strategies for debugging build failures, runtime errors, writing complete output files (ICS/JSON/config), and constraint satisfaction tasks.
systematic-exploration
Strategies for avoiding dead ends and premature conclusions. Read this when stuck or when an approach seems to not work.
blindness-deafness
In D&D, Blindness/Deafness selectively removes one sense — the target can still act but loses critical awareness. The real-world version is selective channel muting: blocking a process from seeing certain inputs (input filtering, API response redaction), deafening it to specific signals (suppressing webhooks, ignoring…
longstrider
Longstrider is the optimization spell for systems that already work. It makes the path shorter without changing the destination. It cares about sustained pace, not flashy one-off benchmarks.
mage-hand
Use this skill for small, careful remote manipulations where dexterity matters more than force.