Borrowing it
Nothing to install: this file belongs to openclosed-org/axum-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/openclosed-org/axum-harness/main/.agents/skills/harness-diagnose/SKILL.mdgit clone --depth 1 https://github.com/openclosed-org/axum-harnessWrote 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/openclosed-org/axum-harness/harness-diagnose)<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/harness-diagnose"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/harness-diagnose/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/openclosed-org/axum-harness/harness-diagnose"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/harness-diagnose.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.00056 | $0.00425 |
| Opus 5 | $0.00028 | $0.00212 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
harness-diagnose 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 11d 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
Harness Diagnose
Use this skill for bugs and regressions.
Workflow skills guide process. Ownership skills still decide writable boundaries.
Phases
- Build a feedback loop.
- Reproduce the exact symptom.
- Generate 3-5 ranked falsifiable hypotheses.
- Instrument one boundary or variable at a time.
- Fix the smallest causal closed loop.
- Add regression evidence at the same semantic level.
- Run path-scoped gates from
agent/manifests/gate-matrix.yml. - Report evidence and residual uncertainty.
Feedback Loop Options
Prefer fast, deterministic, agent-runnable signals:
- failing unit, service, integration, replay, or contract test
- validator or gate command
- CLI invocation with fixture input and expected output
- HTTP request against a running server
- replayed event, outbox, or projector trace
- throwaway harness isolated to one service, server, worker, or repo-tool path
- stress loop for flakes or concurrency issues
If no credible loop can be built, stop and state what was tried and what artifact is needed.
Instrumentation Rules
- Every probe must test one hypothesis.
- Prefer debugger, targeted assertion, or narrow logs over broad logging.
- Tag temporary logs with a unique prefix and remove them before completion.
- For performance regressions, measure first and fix second.
Completion Report
State:
- violated invariant
- causal boundary: contract, service, server, worker, platform, tooling, docs, or cross-boundary
- repair made
- regression evidence added or why no correct seam exists
- gates run
- gates not run
- residual risk or uncertainty
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.
- 11d ago First seen · 58 lines · 56 tokens per session scan A 419b63cb8d55
harness-diagnose is a skill published in the GitHub repository openclosed-org/axum-harness (49 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 425 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
open_rca_diagnosis
A structured method for finding the root cause of failures in microservices by examining measurements, request traces, and logs. It uses thresholds and cross-checks to connect symptoms to causes.
files-inspect
Inspect, download, upload, and debug Kurtosis file artifacts. View artifacts in an enclave, download them locally for inspection, upload local files, and troubleshoot file mounting issues. Use when services can't find expected files or configs are wrong.
starlark-dev
Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.
docker-debug
Debug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.
enclave-inspect
Inspect and manage Kurtosis enclaves. List enclaves, view services and ports, examine file artifacts, dump enclave state for debugging, and clean up. Use when you need to understand what's running inside an enclave or export its state.
k8s-debug-pods
Debug Kurtosis pods on Kubernetes. Diagnose why pods are Pending, CrashLoopBackOff, ImagePullBackOff, or Evicted. Check node taints, tolerations, resource pressure, and pod events. Use when kurtosis engine start fails or pods aren't coming online.