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 guyuefangyuanl/deepseek-better-harness --skill harness-project-readinessgit clone --depth 1 https://github.com/guyuefangyuanl/deepseek-better-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/guyuefangyuanl/deepseek-better-harness/harness-project-readiness)<a href="https://agentmods.dev/skills/guyuefangyuanl/deepseek-better-harness/harness-project-readiness"><img src="https://agentmods.dev/badge/skills/guyuefangyuanl/deepseek-better-harness/harness-project-readiness/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/guyuefangyuanl/deepseek-better-harness/harness-project-readiness"><img src="https://agentmods.dev/badge/skills/guyuefangyuanl/deepseek-better-harness/harness-project-readiness.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.00216 |
| Opus 5 | $0.00028 | $0.00108 |
| Sonnet 5 | $0.00011 | $0.00043 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
harness-project-readiness 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 Project Readiness
Review the repository path from intent to verified change.
- Read the nearest repository instructions and the explicit request, spec, or acceptance criteria before inspecting implementation details.
- Bound the current change with version-control status and diff evidence.
- Trace affected entry points, owners, tests, generated outputs, and high-risk boundaries such as credentials, migrations, deployment, or destructive work.
- Prefer executable repository checks over prose claims. Distinguish tests run, tests merely present, and checks unavailable.
- Return only findings with a concrete consequence, evidence, smallest owner, repair direction, and verifier.
Read references/project-readiness-contract.md for severity and output rules.
What ships with it
1 file 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.
- 11d ago First seen · 22 lines · 56 tokens per session scan A 341b8a6aeb93
harness-project-readiness is a skill published in the GitHub repository guyuefangyuanl/deepseek-better-harness (1 stars, last pushed 21d ago), licensed MIT. It adds 56 tokens to every session and 216 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-31.
Other skills, from other repositories
daytona-windows-cert
Run the verified Windows repro for iPolloWork enterprise TLS behavior: install a fake corporate CA into the Windows machine store, serve healthy and broken HTTPS control planes, install a Windows build, and prove the desktop app and spawned runtimes use the operating system trust path.
daytona-recording-artifacts
Use this skill to collect proof that a Daytona UI flow works. Use fraimz before declaring the flow passed. If the user asks to do e2e tests for a feature, frame proof is required unless they explicitly ask for non-UI or mock-only validation.
fraimz
create a fraimz, make fraimz, prove it works, frame proof, PR proof, validate experience, e2e evidence, fraimz.html. The full fraimz loop — frame the claim, drive the real app via CDP, validate/repair, output fraimz.html. Use whenever a task ends with "please create a fraimz" or any change needs end-to-end proof.
daytona-electron-den
Electron and Den, desktop plus cloud, two-sandbox e2e, cloud auth, marketplace, org policy, worker proxy, provider sync, desktop handoff. Validate Electron against a Daytona Den server with unified proof.
run-evals
Launch a real iPolloWork app and run coded eval flows against it. This skill owns launch + run; the prove/repair/verdict loop and evidence standard live in the fraimz skill — load that too for anything that ends in a verdict.
delivery-proof
Delivery proof and the doublecheck report. Use when the work is done and the delivery must be proven — consolidate the spec, test timeline, review verdicts, and verification checks into a doublecheckreport, and only then claim completion.