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 waqas1412/claude-harness --skill prgit clone --depth 1 https://github.com/waqas1412/claude-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/waqas1412/claude-harness/pr)<a href="https://agentmods.dev/skills/waqas1412/claude-harness/pr"><img src="https://agentmods.dev/badge/skills/waqas1412/claude-harness/pr/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/waqas1412/claude-harness/pr"><img src="https://agentmods.dev/badge/skills/waqas1412/claude-harness/pr.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.00000 | $0.01316 |
| Opus 5 | $0.00000 | $0.00658 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
pr 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR description (house standard, profile-driven)
First, load .claude/harness/profile.md for this project's tokens (REPO, TICKET_PREFIX,
TRACKER_BROWSE_URL, TRACKER_CLOSE_KEYWORD, DEFAULT_BRANCH, COMMIT_TYPES, LINT_CMD,
UNIT_TEST_CMD, E2E_TEST_CMD, BUILD_CMD). In a multi-repo profile the four command tokens are
the per-repo table's Lint / Test / Build / E2E columns for the repo you are in, and - there means the
step genuinely does not exist. If no profile exists, infer from the repo
(run /harness-init to create one) and proceed; if there is no tracker, use GitHub Fixes #<n> and
drop the tracker-close line.
Title (goes in GitHub's title field, NOT the body)
<type>: <TICKET-KEY> <imperative one-line summary>
- type is one of
COMMIT_TYPES(default: feat | fix | refactor | chore | perf | docs | test). - Append
!for a breaking change (e.g.feat!: <TICKET-KEY> ...). Optional module scope:feat(area): .... <TICKET-KEY>usesTICKET_PREFIX(e.g.PROJ-1234); omit if the project has no tracker.- Must stand alone in history; never "fix", "updates", "phase 1".
Body
The body is a tracker close line plus a compact summary of what changed and why. Nothing else: no section headings, no Testing block, no Screenshots table, no breaking-changes assertion, no notes-for-review.
Bullets are the shape, not a paragraph: 3 to 6 short bullets, one line each, each naming a change and its why. Fall back to a single sentence only when the change is genuinely one idea and a lone bullet would look odd. Never a wall of prose, and never a file-by-file restatement.
The close line is a link: <TRACKER_CLOSE_KEYWORD> [<TICKET-KEY>](<TRACKER_BROWSE_URL><TICKET-KEY>).
When there is no ticket, open the body with the source thread as a link instead. When the work came
from someone's report, close the body with Reported by <name> in [#channel](<url>).
A body describes the head it is on. Whenever a commit lands, the scope moves, or review feedback lands, reconcile the body in the same step rather than leaving it describing an older head.
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.
- 2d ago Changed · +12 lines da18be8c5e1f
- 6d ago Changed · +15 lines · -103 tokens per session 972c1bef390e
- 10d ago First seen · 42 lines · 103 tokens per session scan A 08e91f018003
pr is a skill published in the GitHub repository waqas1412/claude-harness (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,316 tokens. 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
fabrik-review-comment
Use when operating as the Fabrik Review comment reviewer. This skill guides applying user decisions on review findings — fixing issues, dismissing false positives, or deferring items — then committing and pushing without signaling stage completion.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.
flame-harness-submit
Phase 10 — upload store text metadata + categories via fastlane, then pause with exact manual steps for the final iOS review submission and Android production promotion.
develop-feature
Autonomously implement a complete feature from request to merge-ready — documentation phase, wave-based TDD implementation, then all quality gates, without stopping for human input.
flame-harness-build
Phase 8 — bootstrap signing credentials, generate fastlane config from templates, and build + upload signed IPA (TestFlight) and AAB (internal track).