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 agentmods add skills/gabrieldabbah/genesis/test-gatenpx skills add gabrieldabbah/genesis --skill test-gategit clone --depth 1 https://github.com/gabrieldabbah/genesisWrote 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/gabrieldabbah/genesis/test-gate)<a href="https://agentmods.dev/skills/gabrieldabbah/genesis/test-gate"><img src="https://agentmods.dev/badge/skills/gabrieldabbah/genesis/test-gate.svg" alt="Measured on agentmods" 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.00136 | $0.01451 |
| Opus 5 | $0.00068 | $0.00726 |
| Sonnet 5 | $0.00027 | $0.00290 |
| Haiku 4.5 | $0.00014 | $0.00145 |
Grade A, and why
test-gate 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 6d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Gate — verify before commit, block on red
Overview
Run the project's full Tier-B battery, read the real output, and
stop the moment anything is red — never commit a red tree, never claim "passing" you did not watch pass.
The strategy this enforces is the project's docs/TESTING.md. Invocation is the
authorization — run end-to-end without a confirm prompt.
This is the project's concrete runner, built from its own commands and infra. Closing ritual:
test-gate green, then commit, then /generate-pr.
Arguments & modes
$1=full(default) — the Tier-B PR-gated battery (what blocks a commit/merge).$1=fast— Tier-A local loop (unit + property + lint), skips Docker/integration for a tight feedback cycle.fastgreen is not sufficient to commit — runfullbefore committing.
Step 0 — Discover the commands (deterministic — never guess them)
Read the source of truth; do not invent commands:
sed -n '/## Commands/,/^## /p' CLAUDE.md # the canonical command list
cat docs/TESTING.md # tiers, kinds, the Docker infra block, the gate order
ls docker-compose*.y*ml 2>/dev/null # is there hermetic infra to bring up?
Map what you find to the gate stages and set a shell var per stage from the real discovered command —
$LINT, $TYPECHECK, $TEST (the Tier-B suite), $E2E, and $MIGRATE / $SEED for infra. If a stage
has no command in this project, leave its var empty, skip it, and say so in the report (an honest "no
e2e configured" — never a silent pass). Never read or print .env or secrets: to check a needed
var, test presence only ([ -n "$VAR" ] && echo set).
Step 1 — Bring up hermetic infra (only if a compose file exists)
COMPOSE=$(ls docker-compose.test.y*ml docker-compose.y*ml 2>/dev/null | head -1)
if [ -n "$COMPOSE" ]; then
docker compose -f "$COMPOSE" up -d --wait # wait for healthchecks; don't race startup
trap 'docker compose -f "$COMPOSE" down -v' EXIT # ALWAYS tear down + drop volumes, even on failure
[ -n "$MIGRATE" ] && eval "$MIGRATE"; [ -n "$SEED" ] && eval "$SEED" # deterministic schema + fixtures
fi
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.
- 6d ago First seen · 97 lines · 136 tokens per session scan A 6ae34fe64c45
test-gate is a skill published in the GitHub repository gabrieldabbah/genesis (4 stars, last pushed 1mo ago), licensed MIT. It adds 136 tokens to every session and 1,451 once invoked, about $0.0007 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
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave in isolated worktrees, collects discoveries, shares context between waves. Use when work decomposes into 3+ independent streams that can run simultaneously.
daemon
Continuous autonomous operation mode. Keeps campaigns running 24/7 by chaining Claude Code sessions via RemoteTrigger. Each session picks up from the campaign's continuation state, works until context runs low or the phase completes, then schedules the next session. Auto-stops on campaign completion or budget…
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
setup
First-run experience for the harness. Three modes: Recommended (guided, 3 min), Full Tour (guided + skill walkthrough, 8 min), and Express (zero questions, 30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…