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 thaifurforo/ai-toolkit --skill harness-tasksgit clone --depth 1 https://github.com/thaifurforo/ai-toolkitWrote 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/thaifurforo/ai-toolkit/harness-tasks)<a href="https://agentmods.dev/skills/thaifurforo/ai-toolkit/harness-tasks"><img src="https://agentmods.dev/badge/skills/thaifurforo/ai-toolkit/harness-tasks/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/thaifurforo/ai-toolkit/harness-tasks"><img src="https://agentmods.dev/badge/skills/thaifurforo/ai-toolkit/harness-tasks.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.00072 | $0.00770 |
| Opus 5.5 | $0.00029 | $0.00308 |
| Sonnet 5.5 | $0.00014 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
harness-tasks scanned grade A with 1 finding 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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Gate: [comando: npm test / curl / etc.] How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness: Breakdown de Tasks (Etapa 04)
Persona: Tech lead especialista em planejamento ágil.
Integrações
Verificar disponibilidade antes de usar (consultar
harness.config.yaml). Se não disponível → usarharness-engineering/references/12-fallback-skills.md.
writing-plans(se disponível) — estruturar e persistir o plano; fallback:12-fallback-skills.md § writing-plansdispatching-parallel-agents(se disponível) — para tasks independentes em paralelo; fallback:12-fallback-skills.md § dispatching-parallel-agentsusing-git-worktrees(se disponível) — quando múltiplos agentes rodam em paralelo; fallback: branches sequenciaistlc-spec-driven(se disponível) — auto-skip para 1–2 tasks óbvias
Entrada obrigatória
- PRD + arquitetura
- Se o projeto tiver UI: também
.catalog/interface.md(+ assets/mockups em.catalog/assets/interface/). Se faltar → invocarharness-interfaceantes. - Tasks de UI devem referenciar mockups/assets do
.catalogquando existirem (Reuses:/Where:/ descrição).
Formato de User Story
ID: US-[N] | Requisito: RF-[N]
Como [persona], quero [ação], para que [benefício].
CA-01: [critério mensurável]
Estimativa: P/M/G/XG | Deps: US-XX ou nenhuma
Formato de Task Técnica (compatível com TLC)
T-[N] | US-[N] | [Descrição]
Where: [arquivo/módulo]
Done when: [condição objetiva]
Gate: [comando: npm test / curl / etc.]
Depends: [T-XX ou nenhuma]
Reuses: [componente existente ou nada]
Parallel: [sim/não]
Regra de Branch por Dependência
| Situação | Base da branch | PR aponta para |
|---|---|---|
| T-XX sem dependência | develop |
develop |
T-XX com Depends: T-YY |
feature/T-YY |
feature/T-YY |
| T-YY foi mesclada em develop | develop (rebase) |
develop |
Estimativas
P = horas | M = 1–2 dias | G = 3–5 dias | XG = >5 dias (quebrar em tasks menores)
Saída Esperada
- Hierarquia e rastreamento conforme
project_tracking.tool— verharness-engineering/references/11-project-tracking.md - Documentação de entrega em
[delivery_docs.path]/apenas quandoproject_tracking.tool: localou fallback markdown
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.
- 13d ago Changed · +6 lines · +18 tokens per session 540d29900506
- 2mo ago First seen · 65 lines · 54 tokens per session scan A f81d9e53e7e3
harness-tasks is a skill published in the GitHub repository thaifurforo/ai-toolkit (5 stars, last pushed 14d ago), licensed MIT. It adds 72 tokens to every session and 770 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…