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 kivo360/OmoiOS --skill test-writergit clone --depth 1 https://github.com/kivo360/OmoiOSWrote 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/kivo360/omoios/test-writer)<a href="https://agentmods.dev/skills/kivo360/omoios/test-writer"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/test-writer/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/kivo360/omoios/test-writer"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/test-writer.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.00012 | $0.01684 |
| Opus 5 | $0.00006 | $0.00842 |
| Sonnet 5 | $0.00002 | $0.00337 |
| Haiku 4.5 | $0.00001 | $0.00168 |
Grade A, and why
test-writer 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Writer
Generate comprehensive tests following testing best practices.
Test Types
| Type | Purpose | Speed | Isolation |
|---|---|---|---|
| Unit | Single function/class | Fast (<1s) | Complete |
| Integration | Multiple components | Medium (<10s) | Partial |
| E2E | Full workflow | Slow (<60s) | None |
| Property | Invariants over inputs | Varies | Complete |
Python Testing with Pytest
Unit Test Template
"""Test {module} {component}.
Tests Requirements: REQ-{XXX}-001
"""
import pytest
from unittest.mock import Mock, patch
from module import Component
@pytest.fixture
def component():
"""Create component with test dependencies."""
return Component(
dependency=Mock(),
config={"test": True}
)
class TestComponent:
"""Tests for Component class."""
def test_method_returns_expected_when_valid_input(self, component):
"""Method returns expected result for valid input."""
# Arrange
input_data = {"key": "value"}
expected = {"result": "processed"}
# Act
result = component.method(input_data)
# Assert
assert result == expected
def test_method_raises_when_invalid_input(self, component):
"""Method raises ValueError for invalid input."""
with pytest.raises(ValueError, match="Invalid input"):
component.method(None)
@pytest.mark.parametrize("input_val,expected", [
("a", 1),
("b", 2),
("c", 3),
])
def test_method_handles_various_inputs(self, component, input_val, expected):
"""Method handles different input values correctly."""
assert component.method(input_val) == expected
Integration Test Template
"""Integration tests for {feature}.
Tests end-to-end flow of {workflow}.
"""
import pytest
from httpx import AsyncClient
from app.main import app
from app.database import get_db
@pytest.fixture
async def client():
"""Create test client with database."""
async with AsyncClient(app=app, base_url="http://test") as client:
yield client
@pytest.fixture
async def db_session():
"""Create isolated database session."""
# Setup
session = await create_test_session()
yield session
# Teardown
await session.rollback()
class TestFeatureWorkflow:
"""Integration tests for feature workflow."""
@pytest.mark.asyncio
async def test_complete_workflow(self, client, db_session):
"""Test complete create-read-update-delete workflow."""
# Create
response = await client.post("/api/items", json={"name": "test"})
assert response.status_code == 201
item_id = response.json()["id"]
# Read
response = await client.get(f"/api/items/{item_id}")
assert response.status_code == 200
assert response.json()["name"] == "test"
# Update
response = await client.put(
f"/api/items/{item_id}",
json={"name": "updated"}
)
assert response.status_code == 200
# Delete
response = await client.delete(f"/api/items/{item_id}")
assert response.status_code == 204
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 · 290 lines · 12 tokens per session scan A 1f453dee809c
test-writer is a skill published in the GitHub repository kivo360/OmoiOS (77 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,684 once invoked, about $0.0001 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-30.
Other skills, from other repositories
test-reporting
Run the Level 2 dummy agent integration test suite and produce a detailed HTML report with per-test input → outcome analysis.
test-generator
Generate pytest test cases for Python functions and classes.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
accessibility-testing
Skill "accessibility-testing" from vibeeval/vibecosystem, covering accessibility testing, axe-core setup, jest-axe (unit / component tests), playwright-axe (e2e) and cypress-axe.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.
test-generator
Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.