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 skills add SummerEngine/summer-engine-agent --skill character-portraitgit clone --depth 1 https://github.com/SummerEngine/summer-engine-agentWrote 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/skills/summerengine/summer-engine-agent/character-portrait)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/character-portrait"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/character-portrait/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/skills/summerengine/summer-engine-agent/character-portrait"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/character-portrait.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.02896 |
| Opus 5.5 | $0.00030 | $0.01158 |
| Sonnet 5.5 | $0.00015 | $0.00579 |
| Haiku 4.5 | $0.00008 | $0.00290 |
Grade A, and why
character-portrait 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 2mo 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
character-portrait — Locked Bust for Dialogue UI
This skill produces ONE polished character portrait — bust or shoulders-up framing, neutral or stylized background, designed to drop into a dialogue UI, character-select screen, or lore card. It is the opposite of summer:2d-assets/concept-art: concept art explores; this skill commits.
The single biggest failure mode is inconsistency across a cast. Generating five party members one at a time without a locked anchor produces five images that look like they're from five different games — different lighting, different angle, different palette, different rendering style. This skill makes you write a locked anchor suffix the first time and re-use it verbatim for every subsequent portrait.
If the user is still exploring the look, this is the wrong skill — route to summer:2d-assets/concept-art first, lock a direction, then come back here. The summer:asset-pipeline/asset-strategy meta-router asks "Quick check — exploring the look (3-4 variants for art direction) or generating a final character portrait for dialogue UI?" to disambiguate.
When to use
- "Generate a portrait for the merchant NPC."
- "I need a character-select image for the four playable heroes."
- "Make a lore-card image of the king."
- "Add a VN-style dialogue portrait for Aria."
- The cast is locked and the visual direction is locked; you're producing finals.
When NOT to use
- The user is still exploring →
summer:2d-assets/concept-art. - The user wants pixel art →
summer:2d-assets/pixel-art. - The user wants a full-body 3D model →
summer:asset-pipeline/asset-strategy. - The user wants 4+ animated expressions of the same character — generate one base portrait here, then use img2img with the base as
referenceImageUrlfor each expression.
Steps
1. Read or establish the locked anchor
Check .summer/portrait-anchor.md first.
Read .summer/portrait-anchor.md
If it doesn't exist, this is the first portrait in the cast — you must define the anchor now. Ask the user (or infer from .summer/GameSoul.md):
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.
- 2mo ago First seen · 202 lines · 76 tokens per session scan A 93914ba22557
character-portrait is a skill published in the GitHub repository SummerEngine/summer-engine-agent (59 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 2,896 once invoked, about $0.0003 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 skills, from other repositories
self-evolve
Capture reusable patterns from a finished project and lift them into framework-level priors (contracts, modules, skeletons) that future projects inherit. Run only when the user explicitly requests self-evolution; the orchestrator executes the workflow.
artist-self-evolve
Distill stable art-generation patterns from a completed project, so future projects produce comparable assets without re-discovering the prompts. Lead-dispatched only — orchestrator invokes this skill from its self-evolve flow with a game-slug message; do not self-trigger.
vibegame-build
Run VibeGame's standard end-to-end game development workflow with reviewer gates. Use when the user wants to create a game from zero or evolve an existing game across multiple stages.
vibegame-start
Resume a VibeGame orchestrator session after vibegame start. Use at the beginning of a Claude or Codex session to inspect team runtime state, repair missing persistent members, load goal and GDD context, inspect tasks, and ask the user what to do next.
vibegame-edit
Iterate broadly on an existing game, on top of vibegame-build. Use when the user asks to change an existing game's art style, genre, or core rules. Not for local tuning such as numbers or game feel. Orchestrator only.
hearth-feel
Make a Hearth game feel good, not just run — the juice stack (hit-stop, screen shake, flash, particle bursts, layered sound), tween easing, camera effects, anticipation/recovery animation idioms, game-UX conventions (menus, pause, onboarding, difficulty, save etiquette), effect-asserting playtests, and the quality bar…