Borrowing it
Nothing to install: this file belongs to schmitthub/clawker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/schmitthub/clawker/main/.agents/skills/writing-tests/SKILL.mdgit clone --depth 1 https://github.com/schmitthub/clawkerWrote 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/schmitthub/clawker/writing-tests)<a href="https://agentmods.dev/skills/schmitthub/clawker/writing-tests"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/writing-tests/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/schmitthub/clawker/writing-tests"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/writing-tests.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.09475 |
| Opus 5.5 | $0.00000 | $0.03790 |
| Sonnet 5.5 | $0.00000 | $0.01895 |
| Haiku 4.5 | $0.00000 | $0.00948 |
Grade A, and why
writing-tests 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 1mo 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.
res := h.RunInContainer("dev", "curl", "-s", "https://api.anthropic.com") How it starts
The opening of the file, as written. The whole thing — 977 lines — stays where its author put it; the contents beside it link to each section on GitHub.
writing-tests
Extended test patterns and examples. For the mandatory rules, see the Testing rules section of the root
AGENTS.md.
Testing Philosophy: DAG-Driven Test Infrastructure
The Core Principle
Clawker's packages follow a strict DAG (Directed Acyclic Graph):
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Foundation │ ──▶ │ Middle │ ──▶ │ Composite │ ──▶ │ Commands │
│ Packages │ │ Packages │ │ Packages │ │ │
├─────────────┤ ├─────────────┤ ├─────────────┤ ├─────────────┤
│ git, logger │ │ bundler │ │ docker, │ │ cmd/* │
│ iostreams │ │ │ │ workspace │ │ │
│ config │ │ │ │ │ │ │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
│ │ │
▼ ▼ ▼
gittest/ docker/mocks/ Factory DI
config/mocks/ whailtest/ + runF seam
Each node in the DAG must provide test infrastructure for its dependents.
When every node provides fakes/mocks/stubs, any tier can independently test by mocking the entire chain below it.
Test Seams in Clawker
1. Factory Pattern DI
Factory fields are closures that return dependencies. Tests inject fakes:
f := &cmdutil.Factory{
IOStreams: tio,
Client: func(ctx context.Context) (*docker.Client, error) {
return fake.Client, nil // Fake from docker/mocks
},
Config: func() (config.Config, error) {
return configmocks.NewBlankConfig(), nil
},
// ... other fields
}
2. runF Test Seam
Every command constructor accepts runF to intercept execution:
// Tier 1: Flag parsing only (intercept before run)
var captured *RunOptions
cmd := NewCmdRun(f, func(ctx context.Context, opts *RunOptions) error {
captured = opts
return nil // Don't actually run
})
// Tier 2: Full execution with injected deps
cmd := NewCmdRun(f, nil) // nil = real run function with Factory's fakes
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.
- 1mo ago First seen · 977 lines · 0 tokens per session scan A e08bb4ad6542
writing-tests is a skill published in the GitHub repository schmitthub/clawker (58 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,475 tokens. 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-09-08.
Other skills, from other repositories
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
timeouts-and-async
Make Ginkgo specs interruptible and test asynchronous behavior — SpecContext/context.Context cancellable nodes, NodeTimeout/SpecTimeout/GracePeriod, the --timeout flag, Abort and SIGINT behavior, Gomega Eventually/Consistently (the func(g Gomega) form, .WithContext), and the defer GinkgoRecover() rule for goroutines.…
setup
Wire Ginkgo into a Go package — install the ginkgo CLI and Ginkgo+Gomega, ginkgo bootstrap to generate the suitetest.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs), the package xxxtest convention, dot-import alternatives (aliased import, dsl/ subpackages, --nodot), ginkgo generate, and testing.T interop via…
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…
eng-test-conventions
Go test-shape discipline for Compozy. Use when writing or editing test.go under cmd or internal after test placement is justified. Do not use for non-Go tests, fixture-only changes, or as a replacement for eng-consolidate-test-suites.