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.
git clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/gan-build)<a href="https://agentmods.dev/commands/fmarzochi/egc/gan-build"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/gan-build/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/commands/fmarzochi/egc/gan-build"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/gan-build.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.00016 | $0.00821 |
| Opus 5.5 | $0.00006 | $0.00328 |
| Sonnet 5.5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
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 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.
This is a copy
95% identical to gan-build — 14 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 — 104 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.
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.
- 1mo ago First seen · 104 lines · 16 tokens per session scan A 1827537f19cf
gan-build is a command published in the GitHub repository Fmarzochi/EGC (68 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 821 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to gan-build, differing in 14 lines, and is treated as a copy.
Other commands, from other repositories
test-browser
Run browser tests on pages affected by current PR or branch.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
ui-aqa-flow-code-analysis
Phase 3 Code Analysis of ui-aqa-flow.
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the 7-stage…
test
Execute comprehensive test suites (unit, integration, e2e) to validate implementation correctness and quality.
e2e-dashboard
Read .cursor/playwright-skills/e2e-dashboard/SKILL.md and follow its instructions exactly. Treat that file's body as your operating instructions for this task. Template files to install live in .cursor/playwright-skills/e2e-dashboard/templates/.