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 hamakyo/okf-skills --skill add-testgit clone --depth 1 https://github.com/hamakyo/okf-skillsWrote 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/hamakyo/okf-skills/add-test)<a href="https://agentmods.dev/skills/hamakyo/okf-skills/add-test"><img src="https://agentmods.dev/badge/skills/hamakyo/okf-skills/add-test/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/hamakyo/okf-skills/add-test"><img src="https://agentmods.dev/badge/skills/hamakyo/okf-skills/add-test.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.00052 | $0.00532 |
| Opus 5 | $0.00026 | $0.00266 |
| Sonnet 5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
add-test 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 9d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Test
When to use
Use this Skill when:
- Existing behavior needs test coverage.
- A regression needs a failing test.
- Edge cases or error paths need explicit coverage.
- A refactor needs safety tests before code changes.
Do not use this Skill when:
- The expected behavior is unclear.
- The requested work requires implementation before tests can be meaningful.
- The task is primarily documentation or OKF maintenance.
Inputs
- Target behavior, file, bug, or coverage gap.
- Expected behavior.
- Existing test command or framework, if known.
- Related OKF documents when behavior is domain-specific.
Required context
Before editing tests, read:
- Existing tests near the target area.
- Test helpers, fixtures, factories, and naming conventions.
- Relevant implementation only enough to understand test boundaries.
- Relevant OKF documents when they define expected behavior.
Workflow
- Identify the expected behavior and source of truth.
- Inspect nearby tests to match style, structure, naming, and helpers.
- Choose the right test level: unit, integration, end-to-end, or snapshot.
- Add focused tests for useful cases:
- Normal path.
- Error or invalid input path.
- Boundary values or edge cases.
- Prefer stable assertions over brittle implementation details.
- Run the new test directly.
- Run related test files or suites when risk warrants it.
- If tests expose a defect, stop and report it unless the user asked to fix it.
Guardrails
- Do not change production behavior unless explicitly asked.
- Do not rewrite the test framework or large fixtures for a narrow test request.
- Do not add tests that only assert mocks were called unless that is the meaningful contract.
- Do not hide flaky tests by weakening assertions without explanation.
- Do not add secrets, credentials, private URLs, or personal data to fixtures.
Completion checklist
- Existing test style was followed.
- Test scope matches the behavior.
- Normal, error, and boundary cases were considered.
- New tests were run directly where possible.
- Any failing behavior is clearly reported.
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.
- 9d ago First seen · 77 lines · 52 tokens per session scan A 3936fe44d18e
add-test is a skill published in the GitHub repository hamakyo/okf-skills (2 stars, last pushed 19d ago), licensed MIT. It adds 52 tokens to every session and 532 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
reproducibility-validate
Run a workflow multiple times and compare outputs to produce a similarity score and pass/fail verdict.
eval-agent
Run evaluation tests against an agent to assess quality and archetype resistance.
eval-workflow
Run evaluation tests against a multi-agent workflow to assess orchestration quality and failure archetype resistance.
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
auto-test-execution
Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern.