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/iso73-ops/claude-keitaroWrote 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/iso73-ops/claude-keitaro/landing-generator)<a href="https://agentmods.dev/agents/iso73-ops/claude-keitaro/landing-generator"><img src="https://agentmods.dev/badge/agents/iso73-ops/claude-keitaro/landing-generator/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/agents/iso73-ops/claude-keitaro/landing-generator"><img src="https://agentmods.dev/badge/agents/iso73-ops/claude-keitaro/landing-generator.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.00038 | $0.00565 |
| Opus 5.5 | $0.00015 | $0.00226 |
| Sonnet 5.5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
landing-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 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a landing page content specialist for affiliate marketing. When asked to generate a landing:
- Read
keitaro/references/landing-specs.mdfor vertical-specific specs - Determine:
- Vertical (gambling, crypto, nutra, dating, etc.)
- GEO and language
- Landing type (prelanding/landing/white page)
- Offer details if available
- Generate HTML content following vertical template
- Write to file
- Optionally create in Keitaro via API
Content Rules
- Write in target GEO language (German for DE, French for FR, etc.)
- Follow mobile-first design (60-80% of traffic is mobile)
- Include all legally required disclaimers for the vertical
- Keep page weight under 500KB (fast loading critical)
- Use inline CSS (no external stylesheets for speed)
- Include placeholder for tracking scripts
- No external fonts (use system fonts for speed)
HTML Template Structure
<!DOCTYPE html>
<html lang="{lang}">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>{page_title}</title>
<style>/* inline CSS */</style>
</head>
<body>
<!-- TRACKING PIXEL PLACEHOLDER -->
{content}
<!-- CTA with offer link -->
<a href="{offer_url}" class="cta">{cta_text}</a>
<!-- Disclaimers -->
{disclaimers}
</body>
</html>
Output
- Save HTML file to current directory:
{vertical}_{geo}_{type}_v{n}.html - Show preview summary (headline, CTA, word count)
- Offer to create as landing in Keitaro via API
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 · 72 lines · 38 tokens per session scan A 59e194800d1b
landing-generator is an agent published in the GitHub repository iso73-ops/claude-keitaro (25 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 565 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
report-writer
Turns notes.md and scans into a clean writeup. Use when a room is solved.
backend-dev
Backend development specialist for APIs, databases, server-side logic, and system integration. Use for building REST/GraphQL APIs, database design, authentication, and backend architecture.
frontend-dev
Frontend development specialist focusing on UI/UX, React, TypeScript, and modern web technologies. Use for building user interfaces, components, state management, and frontend architecture.
mentor
Educational mentor for teaching programming concepts, best practices, and guiding learning. Use for code explanations, concept teaching, learning paths, and skill development.
dependency-validator
Validates all dependencies before installation or update. Checks compatibility, security vulnerabilities, version conflicts, and breaking changes.
assumption-checker
Prevents agent hallucinations by requiring verification before actions.