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 d-oit/rust-2026-template --skill harnessgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/harness)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/harness"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/harness/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/d-oit/rust-2026-template/harness"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/harness.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.00068 | $0.01578 |
| Opus 5.5 | $0.00027 | $0.00631 |
| Sonnet 5.5 | $0.00014 | $0.00316 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
harness 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: harness
What Is the Harness
Agent = Model + Harness. The harness is the system of feedforward guides (what to do before coding) and feedback sensors (what catches violations after coding). It has two axes:
- Feedforward (guides): Context, constraints, conventions that prevent errors before they happen.
- Feedback (sensors): Automated checks that fire after code changes, providing structured error output.
The harness has two modes:
- Computational: Deterministic checks (fmt, clippy, deny) — always trust the output.
- Inferential: LLM-based guidance (skill docs, agent context) — direction, not commands.
Tool Ownership & Quality Verification
- Canonical Project Quality Command:
./scripts/quality-gates.sh(orcargo run -p xtask -- quality run).xtaskis the single source of truth for project quality tiers (pull-request,protected-branch,scheduled,release) and quality telemetry (.agents/ci/quality-run.json). - Optional Agent Harness Tooling:
do-harness(scripts/setup-harness.sh) provides agent diagnostics (do-harness doctor) and PR readiness checks (do-harness pr review,do-harness pr ready).do-harness.tomldelegates quality checks to./scripts/quality-gates.shto prevent running redundant duplicate Cargo passes. - Non-Interference Rule: Never assume a green status from
do-harnessmeansxtaskchecks ran, or vice versa. Ifdo-harnessis absent or PR context is unavailable, fall back directly to./scripts/quality-gates.shand./scripts/doctor.sh. - Sensor Applicability Rule: The
quality-gatessensor'swhen-changedglobs indo-harness.tomldecide whetherdo-harness verify --changedruns it. Manifest edits need both"Cargo.toml"(workspace root manifest) and"**/Cargo.toml"(workspace member manifests, inside and outsidecrates/). Rust sources and lockfiles match on file shape ("**/*.rs","**/Cargo.lock") so a file in an unknown directory still selects the sensor."Cargo.toml"alone skips member manifests, and bare wildcards like"**"fire on Markdown-only edits. Keep the same rule inconfig/xtask.jsonwhen_changed.
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.
- 8d ago Changed · +1 lines db988218f662
- 9d ago Changed · +6 lines ecb353491770
- 26d ago Changed · +4 lines 7689ffd1e5d0
- 1mo ago Changed · +1 lines b134253992d1
- 1mo ago Changed · +14 lines 85135b8cc5c6
- 1mo ago Changed · +3 lines 1969f0881ec7
- 2mo ago First seen · 69 lines · 68 tokens per session scan A ed8e7b6d1797
harness is a skill published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 1,578 once invoked, about $0.0003 per session on Opus 5.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
yada-yada-yada
Enter Seinfeld Mode. Explain programming, debugging, architecture, and code reviews through observational comedy inspired by Seinfeld. Trigger when the user says "what's the deal", festivus, serenity, yada, soup, shrinkage, sponge-worthy, master of my domain, double dip, newman, vandelay, nostrand, constanza or…
ruview-quickstart
Onboarding and first-run for RuView (WiFi-DensePose) — Docker demo with simulated data, repo build, and the fastest path to a live sensing dashboard. Use when someone is new to RuView or wants the shortest path to "it works on my machine".
onboard
Zero-to-sensing path picker for RuView (WiFi-DensePose) — pick docker-demo, repo-build, or live-esp32 and run the next concrete step.
doca-programming-guide
Use this skill when the user is writing their first DOCA app or asking a library-agnostic programming question — picking a shipped sample to copy and modify, wiring pkg-config + meson (or FFI from Rust / Go / Python against the public C ABI), walking the Core lifecycle (create → configure → start → connect → use →…
openhue
Control Philips Hue lights, rooms, and scenes via the OpenHue CLI. Turn lights on/off, adjust brightness, color, color temperature, and activate scenes.
rust-learner
Learn Rust language features and crate updates. Use when user asks about Rust version changelog, what's new in Rust, crate updates, Cargo.toml dependencies, tokio/serde/axum features, or any Rust ecosystem questions.