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 agentmods add skills/luisfelipemoro/harness-devkit/tasknpx skills add LuisFelipeMoro/Harness-devkit --skill taskgit clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkitWhat 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 | $0.00046 | $0.00782 |
| Opus 5 | $0.00023 | $0.00391 |
| Sonnet 5 | $0.00009 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
task 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the single-task implementation pipeline (no planning phase). If no task is provided, ask first.
Load agent files on demand — never pre-load all at once; use references/output-format.md headers and show a Pipeline Summary after each Verdict.
Machine-checkable behavior contract: skill.spec.yml · dependency ledger: deps.toml (both generated by the skillspec CLI and git-ignored — Claude never loads them) · full sub-task loop detail: references/loop.md.
Contract
- Input: a single coding task (tech stack derived from the existing codebase if present).
- Output: implemented, tested sub-tasks, each with a Verdict and a
[{key}]-prefixedPROGRESS.mdentry at repo root; a PR fromrelease/{slug}-{key}tomain. - Boundary: no full planning phase — starts at Architecture; per sub-task max ~200 lines with a clear interface boundary, split if not independently testable.
- Rules: Coder owns tests + implementation, written against the frozen Test Case table and falsified before handoff; story ACs + that table are the frozen acceptance contract; Reviewer and StressTester run only after QA approval or escalation; unmitigated CRITICAL security is automatic NOT READY. Full forbids in
skill.spec.yml.
Model assignment
Dispatch the Architect on opus; Scrum Master, QA, Reviewer, Stress, Verdict, and the orchestrator on sonnet; the Coder (core + backend/frontend overlay), Tuner, DevOps, and any read-side Explore/mapping sub-agent on haiku (see CLAUDE.md Model assignment table).
Steps
- Delivery setup (once) — derive the slug + key from the task name, create
.worktrees/dlv-{key}/on branchrelease/{slug}-{key}, and run everything inside it, per ../../references/delivery-and-worktree.md. An existing worktree for the key means resume, not recreate. Never commit or merge tomain— the terminal step is a PR from the release branch. - Planning (once) — follow
skills/planning/SKILL.mdfrom Phase 1 (Architecture); run the Backend-Driven Architecture tier check; produce and confirm a Task Manifest (sizing rules and tier check detail in references/loop.md). - Sub-task loop — repeat per sub-task, one at a time (sub-tasks share the delivery worktree, so never dispatch two Coders concurrently): A story (ScrumMaster) → B code — implement to spec, write the specified tests, falsify each (Coder + one tier overlay) → C QA audit + gates → D review + stress (after the QA signal) → E verdict → F checkpoint +
PROGRESS.md. Exact dispatch, routing signals, Bug-Fix Loop, Tuner limits, checkpoint table, and context budget are in references/loop.md. - Finish — when a sub-task is PRODUCTION READY, load
agents/devops.mdfor Docker/CI artifacts; otherwise continue to the next sub-task. When all sub-tasks are done, push the release branch (ask first) and open a PR tomain, then print the final summary.
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 First seen · 28 lines · 46 tokens per session scan A c597daeea436
task is a skill published in the GitHub repository LuisFelipeMoro/Harness-devkit (10 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 782 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…