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-testinggit 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-testing)<a href="https://agentmods.dev/skills/thaifurforo/ai-toolkit/harness-testing"><img src="https://agentmods.dev/badge/skills/thaifurforo/ai-toolkit/harness-testing.svg" alt="Measured on agentmods" 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.00053 | $0.00800 |
| Opus 5 | $0.00026 | $0.00400 |
| Sonnet 5 | $0.00011 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
harness-testing 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness: Testes (Etapa 06)
Persona: QA Engineer.
Integrações
Verificar disponibilidade antes de usar (consultar
harness.config.yaml). Se não disponível → usarharness-engineering/references/12-fallback-skills.md.
test-driven-development(se disponível) — escrever testes antes (invocar também durante implementação); fallback:12-fallback-skills.md § test-driven-developmentverification-before-completion(se disponível) — antes de marcar a etapa como concluída; fallback:12-fallback-skills.md § verification-before-completionfinishing-a-development-branch(se disponível) — após esta etapa — finaliza a branch para o PR; fallback:12-fallback-skills.md § finishing-a-development-branch
Posicionamento Shift-Left
pré-commit: testes unitários (rápidos, determinísticos)
pré-push: testes de integração
CI (por PR): integração + estruturais + contrato
CI semanal: mutation testing
Tipos de Teste a Gerar
1. Testes Unitários (pré-commit)
- Cada função/método em isolamento, dependências mockadas
- Por CA: happy path + falha esperada + caso limite
Estrutura:
describe('[Módulo]', () => {
describe('CA-01: [critério]', () => {
it('should [comportamento] when [condição]', ...)
it('should [falha] when [condição inválida]', ...)
it('should [caso limite] when [valor limite]', ...)
});
});
2. Testes de Integração (CI por PR)
- Fluxo completo: controller → service → repository
- DB em memória ou testcontainers
3. Testes de Contrato de API (CI por PR)
- Status codes corretos por cenário
- Shape do response (campos obrigatórios, tipos)
- Comportamento com input inválido
4. Testes Estruturais (CI por PR) ⭐ mais importantes para harnessability
Verificar que as camadas dependem apenas na direção permitida. Configurar por violação:
- Detectado automaticamente
- Mensagem de erro inclui instrução de remediação inline
- CI bloqueia em caso de violação
Matriz de Cobertura por CA
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.
- 6d ago First seen · 88 lines · 53 tokens per session scan A 58441448fcac
harness-testing is a skill published in the GitHub repository thaifurforo/ai-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 800 once invoked, about $0.0003 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.