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 commands/sifxprime/kodelyth-ecc/gan-buildgit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/commands/sifxprime/kodelyth-ecc/gan-build)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/gan-build"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/gan-build.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.00012 | $0.00842 |
| Opus 5 | $0.00006 | $0.00421 |
| Sonnet 5 | $0.00002 | $0.00168 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
gan-build 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 3d 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.
This is a copy
89% identical to gan-build — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parse the following from $ARGUMENTS:
brief— the user's one-line description of what to build--max-iterations N— (optional, default 15) maximum generator-evaluator cycles--pass-threshold N— (optional, default 7.0) weighted score to pass--skip-planner— (optional) skip planner, assume spec.md already exists--eval-mode MODE— (optional, default "playwright") one of: playwright, screenshot, code-only
GAN-Style Harness Build
This command orchestrates a three-agent build loop inspired by Anthropic's March 2026 harness design paper.
Phase 0: Setup
- Create
gan-harness/directory in project root - Create subdirectories:
gan-harness/feedback/,gan-harness/screenshots/ - Initialize git if not already initialized
- Log start time and configuration
Phase 1: Planning (Planner Agent)
Unless --skip-planner is set:
- Launch the
gan-planneragent via Task tool with the user's brief - Wait for it to produce
gan-harness/spec.mdandgan-harness/eval-rubric.md - Display the spec summary to the user
- Proceed to Phase 2
Phase 2: Generator-Evaluator Loop
iteration = 1
while iteration <= max_iterations:
# GENERATE
Launch gan-generator agent via Task tool:
- Read spec.md
- If iteration > 1: read feedback/feedback-{iteration-1}.md
- Build/improve the application
- Ensure dev server is running
- Commit changes
# Wait for generator to finish
# EVALUATE
Launch gan-evaluator agent via Task tool:
- Read eval-rubric.md and spec.md
- Test the live application (mode: playwright/screenshot/code-only)
- Score against rubric
- Write feedback to feedback/feedback-{iteration}.md
# Wait for evaluator to finish
# CHECK SCORE
Read feedback/feedback-{iteration}.md
Extract weighted total score
if score >= pass_threshold:
Log "PASSED at iteration {iteration} with score {score}"
Break
if iteration >= 3 and score has not improved in last 2 iterations:
Log "PLATEAU detected — stopping early"
Break
iteration += 1
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.
- 3d ago First seen · 105 lines · 12 tokens per session scan A b72a8671d14c
gan-build is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 842 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gan-build, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
maintainer-review-test-coverage
Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).
review-scope
Establish exactly what this review round examines, and write it down for the reviewer or reviewers that follow. You do not judge anything; you make the target precise.
validate
Run the project's own checks and report the truth. You fix nothing and judge nothing beyond pass or fail — running the gate is the whole job.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.