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 ticketgit 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/ticket)<a href="https://agentmods.dev/skills/waqas1412/claude-harness/ticket"><img src="https://agentmods.dev/badge/skills/waqas1412/claude-harness/ticket/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/ticket"><img src="https://agentmods.dev/badge/skills/waqas1412/claude-harness/ticket.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.00808 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
ticket 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracker ticket (minimal, profile-driven)
First, load .claude/harness/profile.md for this project's tokens (TICKET_PREFIX, TRACKER,
TRACKER_BROWSE_URL). If no profile exists, infer from the repo (run /harness-init) and proceed.
Ticket keys use TICKET_PREFIX (e.g. PROJ-1234); if the project has no tracker, write the ticket as
a backlog markdown file and link a GitHub issue instead.
Body
A ticket is a type/parent line, a terse <Area>: <imperative> title, and 2 to 4 bullets (3 is
typical) of what should change and why. Nothing else: no section headings, no user-story formula, no
acceptance criteria, no Out-of-scope block, no implementation notes, no verification gate.
Write it in product language a non-engineer can act on: name the surface, the wrong behavior, and the
wanted behavior. No identifiers, file paths, function names, formulas, library names, or migration
numbers; those live in the PR and the code. When the work came from someone's report, close with
Reported by <name> in [#channel](<url>).
A ticket states only what is true now. Rewriting a stale or wrong ticket means replacing the text, not appending a correction: carry no history of its own earlier versions and no "previously we thought".
The exact template, the Definition of Ready, and the deliberately-skipped list live in
references/ticket-templates.md (in this skill's directory). Read that file when actually drafting
and fill it from the profile tokens.
One template covers every type. The distinction lives in the type field and the title: a bug names the reproduction and the wrong behavior in its prose, a refactor says in its prose that it is behavior-preserving.
Verification is unchanged: when the work is done, lint, build, and change-scoped tests still run fresh and are reported in chat. They are just not restated in the ticket.
Composes with (does not override)
Avoid-em-dash rule; characterization-tests-first (still how a refactor is executed, just not spelled out in the ticket); verify-before-git-ops.
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.
- 3d ago Changed · +10 lines d7e321e630c2
- 6d ago Changed · -1 lines · -100 tokens per session scan B → A 5fbc25b73b4a
- 10d ago First seen · 42 lines · 100 tokens per session scan B c2819dca7691
ticket is a skill published in the GitHub repository waqas1412/claude-harness (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 808 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
onboard
Interviews someone about a software project as a whole — the problem it solves, who it serves, what is in and out of scope, the hard constraints, and the domain vocabulary — and writes it up as a project constitution that every later feature specification inherits. Use this at the start of a project, before any…
fabrik-implement
Use when operating as the Fabrik Implement stage agent. This skill guides the implementation of a planned feature, following the task checklist to produce committed, tested, pushed code on a feature branch.
fabrik-plan
Use when operating as the Fabrik Plan stage agent. This skill guides the design of an implementation approach, producing a concrete plan with task checklist that the Implement stage will follow.
fabrik-setup
Bootstrap a project to use Fabrik (the GitHub-Project-driven SDLC pipeline orchestrator that drives Claude Code workers through Specify/Research/Plan/Implement/Review/Validate stages). Use this skill when the user wants to install, set up, initialize, or get started with Fabrik for the first time — especially when…
forge-prd
Generate a structured PRD (markdown + meta) for a non-trivial build and auto-create a ticket per acceptance criterion (Forge Mission Control Phase 2, WP3 "PRD generator"). Use before starting a non-trivial feature/build, typically right after Deep Learn Mode. Trigger on "write a PRD", "generate a PRD", "scope this…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.