Borrowing it
Nothing to install: this file belongs to strikersam/autonomous-ai-agency. 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/strikersam/autonomous-ai-agency/master/.agents/skills/test-first-executor/SKILL.mdgit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/test-first-executor)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/test-first-executor"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/test-first-executor/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/strikersam/autonomous-ai-agency/test-first-executor"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/test-first-executor.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.00029 | $0.00704 |
| Opus 5 | $0.00015 | $0.00352 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
test-first-executor 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 11d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: test-first-executor
When to Use
Use this skill whenever:
- Adding a new function, class, or FastAPI endpoint
- Fixing a bug (regression test required)
- Adding a new agent tool or router capability
- A reviewer asks "where are the tests?"
Instructions
Step 1 — Identify what needs testing
- What is the expected input/output?
- What are the failure modes?
- Is there a risky edge case (empty input, auth bypass, model unavailability)?
Step 2 — Write the test first
For this repo, tests live in tests/. Match the pattern:
tests/test_<module>.py # mirrors src module name
Test structure template:
"""Tests for <module>.<Class>."""
from __future__ import annotations
import pytest
# imports
# ── Fixtures ──────────────────────────────────────────────────────────────────
@pytest.fixture
def some_fixture():
...
# ── Happy path ────────────────────────────────────────────────────────────────
def test_<function>_<expected_outcome>():
...
# ── Edge cases ────────────────────────────────────────────────────────────────
def test_<function>_raises_on_<bad_input>():
with pytest.raises(SomeError):
...
# ── Regression ────────────────────────────────────────────────────────────────
def test_regression_<issue_description>():
# Previously this caused <symptom>. Fixed in <commit/version>.
...
Step 3 — Confirm the test FAILS before implementation
Run pytest -x tests/test_<module>.py::test_<name>.
A test that passes immediately (before implementation) is not testing the right thing.
Step 4 — Implement until the test passes
Step 5 — Run the full suite
pytest -x
All pre-existing tests must still pass.
Step 6 — Check coverage of risky paths
For any change to admin_auth.py, key_store.py, agent/tools.py:
- Write a test that specifically exercises the security boundary.
- Confirm the test would catch a regression if the boundary were removed.
Acceptance Checks
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.
- 11d ago First seen · 113 lines · 29 tokens per session scan A 7e4efd2356f5
test-first-executor is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 704 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-31.
Other skills, from other repositories
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
story-development
Implement user stories with test-driven development methodology.