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 oyi77/1ai-skills --skill test-agentgit clone --depth 1 https://github.com/oyi77/1ai-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/oyi77/1ai-skills/test-agent)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/test-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/test-agent/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/oyi77/1ai-skills/test-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/test-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.01234 |
| Opus 5.5 | $0.00009 | $0.00494 |
| Sonnet 5.5 | $0.00005 | $0.00247 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
test-agent 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 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.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This agent writes comprehensive test suites that defend observable contracts and fail on plausible bugs. Use it to close coverage on a changed module or to convert a manual reproduction into a regression test. It follows the project's test conventions and keeps the suite deterministic.
Test Agent
Quick Reference — see parent for full agent ecosystem.
The Test Agent writes and maintains test suites that cover not just happy paths but error paths, edge cases, and integration contracts. It analyzes existing code to identify coverage gaps, generates tests that fail on plausible bugs (not trivial pass-throughs), and enforces coverage thresholds across the codebase. Its philosophy: a test that cannot fail on a real bug is worse than no test — it creates false confidence.
When Not to Use
- Simple or one-off tasks — if the task is straightforward, direct execution is faster than structured methodology.
- Already established workflows — follow existing team conventions rather than introducing new frameworks.
- When automation overhead exceeds benefit — for very small scopes, the setup cost may not be justified.
Dependencies
- Python 3.8+ or Node.js 18+
- Access to relevant APIs/services for your specific use case
- Basic understanding of the domain concepts
Commands
# Refer to the skill's usage section for specific commands
# Adapt these to your workflow
Key Responsibilities
- Coverage gap analysis: Profile the existing test suite to find uncovered branches, error paths, and edge cases — not just line coverage
- Generate meaningful tests: Write tests that defend explicit contracts (inputs → outputs, error states, invariants, transitions) rather than testing implementation details
- Regression test for bugs: For every bug fix, generate a test that reproduces the original failure and confirms it stays fixed
Code Example
"""Minimal test agent pattern — analyze coverage and generate tests."""
import json, sys
from pathlib import Path
def analyze_coverage(source_path: str, test_path: str) -> dict:
"""Identify uncovered functions and generate skeleton tests."""
source = Path(source_path)
tests = Path(test_path)
source_funcs = set()
for file in source.rglob("*.py"):
content = file.read_text()
for line in content.split("\n"):
stripped = line.strip()
if stripped.startswith("def ") and not stripped.startswith("def _"):
name = stripped.split("(")[0].replace("def ", "")
source_funcs.add(name)
test_funcs = set()
for file in tests.rglob("test_*.py"):
content = file.read_text()
for line in content.split("\n"):
stripped = line.strip()
if stripped.startswith("def test_"):
name = stripped.split("(")[0].replace("def ", "")
test_funcs.add(name)
uncovered = source_funcs - test_funcs
return {
"source_functions": sorted(source_funcs),
"test_functions": sorted(test_funcs),
"uncovered": sorted(uncovered),
"coverage_pct": round(len(test_funcs) / max(len(source_funcs), 1) * 100, 1),
"recommendations": [f"Add test for {fn}" for fn in sorted(uncovered)[:10]]
}
if __name__ == "__main__":
result = analyze_coverage(sys.argv[1], sys.argv[2])
print(json.dumps(result, indent=2))
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 Changed · +11 lines 7c60b4120ddc
- 1mo ago First seen · 127 lines · 23 tokens per session scan A b3b064940fb1
test-agent is a skill published in the GitHub repository oyi77/1ai-skills (17 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,234 once invoked, about $0.0001 per session on Opus 5.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
ai-discover
Read-only discovery step of the auto-improvement loop. One bounded agent turn per cycle reads the focus files (Read/Grep/Glob only, no shell, no subagents) and replies with a JSON array of testable surfaces {file, line, symbol, rule, message, hypothesis}; the spine authors fixes and verifies them. Discovery only — no…
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
adk-verify-snippets
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail report with per-snippet coverage. Use when the user asks to verify, test, or validate the code samples in a README, a guide…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
a11y-playwright-testing
Accessibility testing for web applications using Playwright (@playwright/test), TypeScript, and axe-core. Use to write, run, or debug WCAG 2.2 AA checks, keyboard and focus tests, ARIA/semantic validation, accessible names, form labels, color contrast, or screen-reader test patterns. Keywords: accessibility, WCAG…
qa-manual-istqb
Create QA artifacts from requirements: test plans, test conditions/cases, bug reports, regression suites, traceability, and exploratory charters. Use for test planning, test design, defects, coverage, or QA deliverables. Applies ISTQB risk-based techniques and loads templates only when needed. Keywords: test plan…