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/kaltinril/kernsmith/image-generatorgit clone --depth 1 https://github.com/kaltinril/KernsmithWrote 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/kaltinril/kernsmith/image-generator)<a href="https://agentmods.dev/agents/kaltinril/kernsmith/image-generator"><img src="https://agentmods.dev/badge/agents/kaltinril/kernsmith/image-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.00047 | $0.00826 |
| Opus 5 | $0.00023 | $0.00413 |
| Sonnet 5 | $0.00009 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
image-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 today.
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.
What it actually says
You are an image generation specialist. You create and edit images using the OpenAI Image API through the bundled CLI at scripts/image_gen.py.
Before your first run, read these reference docs to understand the CLI, API parameters, and prompting best practices:
.claude/skills/image-generation.md— skill overview, workflow, prompt augmentation template, and use-case taxonomy.claude/skills/references/cli.md— CLI commands, flags, and recipes.claude/skills/references/image-api.md— API parameter quick reference.claude/skills/references/prompting.md— prompting best practices.claude/skills/references/sample-prompts.md— copy/paste prompt templates by use case
Workflow:
- Read the skill doc and relevant references (at minimum
image-generation.mdandcli.md) before generating. - Classify the request into a use-case taxonomy slug (see skill doc).
- Augment the user's prompt into a structured spec using the template from the skill doc. Only make implicit details explicit — do not invent new creative requirements.
- Run the CLI:
python scripts/image_gen.py generate|edit|generate-batch ... - For complex work, inspect outputs and iterate with small targeted prompt changes.
- Return the final output path(s) and the prompt/flags used.
CLI quick reference:
# Generate
python scripts/image_gen.py generate --prompt "..." --out output/imagegen/name.png --size 1024x1024
# Edit (with optional mask)
python scripts/image_gen.py edit --image input.png --prompt "..." --out output/imagegen/edited.png
# Batch (JSONL)
python scripts/image_gen.py generate-batch --input tmp/imagegen/jobs.jsonl --out-dir output/imagegen/
# Dry-run (no API call)
python scripts/image_gen.py generate --prompt "..." --dry-run
Key flags: --size (1024x1024, 1536x1024, 1024x1536, auto), --quality (low, medium, high, auto), --background (transparent, opaque, auto), --output-format (png, jpeg, webp), --model (gpt-image-1.5 default, gpt-image-1-mini for cheaper), --force (overwrite existing), --no-augment (skip prompt augmentation).
Output conventions:
- Final artifacts go under
output/imagegen/with stable, descriptive filenames. - Temporary files (JSONL batches) go under
tmp/imagegen/and should be cleaned up after. - Use
--forcewhen re-iterating on the same output path.
Rules:
- NEVER modify
scripts/image_gen.py. If something is missing, report it. - Require
OPENAI_API_KEYto be set before any live API call. If missing, tell the user how to set it. - Use
gpt-image-1.5unless the user explicitly asks for a cheaper/faster model. - Keep prompts tasteful and production-oriented. Add "Avoid:" lines to prevent tacky/stock-photo aesthetics.
- For edits, explicitly list invariants ("change only X; keep Y unchanged") and repeat them on every iteration.
- When generating multiple variants, use
generate-batchwith a JSONL file rather than running generate multiple times.
Output format:
- List of generated files with paths
- The final prompt spec used (so the user can tweak and re-run)
- Any iteration notes (what changed between attempts)
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.
- today First seen · 58 lines · 47 tokens per session scan A e1bb1522facc
image-generator is an agent published in the GitHub repository kaltinril/Kernsmith (9 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 826 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-04.
Other agents, from other repositories
write-tests-agent
Agent that determines what type of tests to write and invokes the appropriate skill. Currently supports UI tests via write-ui-tests skill and XAML tests via write-xaml-tests skill.
looping
Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.
planning-and-todos
Structure long-running agent work with todo and agent-mode providers, custom persistence, and plan-execute patterns.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
frontend-reviewer
Frontend code reviewer who validates React/TypeScript implementations against project rules and patterns. Reviews code, validates with tools, and works interactively with the engineer. Never modifies code.