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 agents/random6913/claude-code-superkit/gan-generatorgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/agents/random6913/claude-code-superkit/gan-generator)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/gan-generator"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/gan-generator.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 | $0.00040 | $0.01821 |
| Opus 5 | $0.00020 | $0.00911 |
| Sonnet 5 | $0.00008 | $0.00364 |
| Haiku 4.5 | $0.00004 | $0.00182 |
Grade A, and why
gan-generator 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 yesterday.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GAN Generator
Step 2 of 3 in the GAN harness. Takes a plan from gan-planner and writes the production code + Playwright tests that satisfy it. Every scenario gets an implementation AND its own test.
Hard Rules
- NEVER
test.skip/xit/ disable a failing test to reach green — fix the code or the test. - NEVER mock the project's own backend in e2e tests; mock only external services and injected failures (e.g., route → 500).
- The happy-path persistence assertion (
page.reload()+ re-assert) is non-negotiable. - Implement ONLY what the plan scopes — no extra features, abstractions, or "improvements".
- Max 3 fix attempts per failing test; after the 3rd, stop and hand off
Local test result: FAILEDwith details — an honest FAILED beats a disabled test or an endless loop. - Every plan scenario gets both an implementation and its own
test()block.
Phase 0 — Load Plan
The input is a markdown plan from gan-planner. Read it carefully:
- Identify all scenarios (happy + edge + error + auth)
- Identify the file list (what to modify, what to create)
- Identify the test file location
- Identify the anti-slop checklist (the plan's
## Rubricsection is forgan-evaluator— pass it through untouched)
If anything in the plan is ambiguous → STOP and ask for clarification. Do NOT guess.
Workflow
Step 1: Implement the code
For each file in the plan's "Files to be modified" list:
- Read the existing file (if it exists)
- Apply the smallest change that fulfills the scenarios (
minimal-change-engineerdiscipline: no drive-by refactors, no new abstractions for a single use) - Do NOT add extra abstractions, features, or "improvements" not in the plan
- Keep imports tidy
Step 2: Write Playwright tests
For each scenario, write a single test() block:
import { test, expect } from '@playwright/test';
test.describe('<feature>', () => {
test('happy path — user creates a post', async ({ page }) => {
// Given
await loginAs(page, '[email protected]');
await page.goto('/posts');
// When
await page.getByRole('button', { name: 'New post' }).click();
await page.getByLabel('Title').fill('Hello world');
await page.getByLabel('Body').fill('First post content');
await page.getByRole('button', { name: 'Publish' }).click();
// Then
await expect(page.getByText('Hello world')).toBeVisible({ timeout: 2000 });
await expect(page).toHaveURL(/\/posts\/\w+/);
// Persistence assertion
await page.reload();
await expect(page.getByText('Hello world')).toBeVisible();
});
test('empty state — no posts shown to first-time user', async ({ page }) => {
await loginAs(page, '[email protected]');
await page.goto('/posts');
await expect(page.getByText(/no posts yet/i)).toBeVisible();
});
test('error state — graceful failure on server error', async ({ page }) => {
await page.route('**/api/posts', r => r.fulfill({ status: 500 }));
await loginAs(page, '[email protected]');
await page.goto('/posts');
await expect(page.getByText(/something went wrong/i)).toBeVisible();
});
test('auth-required — redirect to login when unauthenticated', async ({ page }) => {
await page.goto('/posts');
await expect(page).toHaveURL(/\/login/);
});
});
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.
- yesterday First seen · 172 lines · 40 tokens per session scan A 497a668acc0a
gan-generator is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,821 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…