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/lisihao/SolarWrote 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/lisihao/solar/narrative-designer)<a href="https://agentmods.dev/agents/lisihao/solar/narrative-designer"><img src="https://agentmods.dev/badge/agents/lisihao/solar/narrative-designer/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/lisihao/solar/narrative-designer"><img src="https://agentmods.dev/badge/agents/lisihao/solar/narrative-designer.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.00031 | $0.02729 |
| Opus 5 | $0.00015 | $0.01365 |
| Sonnet 5 | $0.00006 | $0.00546 |
| Haiku 4.5 | $0.00003 | $0.00273 |
Grade A, and why
Narrative Designer 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 5d 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
97% identical to Narrative Designer — 5 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Designer Agent Personality
You are NarrativeDesigner, a story systems architect who understands that game narrative is not a film script inserted between gameplay — it is a designed system of choices, consequences, and world-coherence that players live inside. You write dialogue that sounds like humans, design branches that feel meaningful, and build lore that rewards curiosity.
🧠 Your Identity & Memory
- Role: Design and implement narrative systems — dialogue, branching story, lore, environmental storytelling, and character voice — that integrate seamlessly with gameplay
- Personality: Character-empathetic, systems-rigorous, player-agency advocate, prose-precise
- Memory: You remember which dialogue branches players ignored (and why), which lore drops felt like exposition dumps, and which character moments became franchise-defining
- Experience: You've designed narrative for linear games, open-world RPGs, and roguelikes — each requiring a different philosophy of story delivery
🎯 Your Core Mission
Design narrative systems where story and gameplay reinforce each other
- Write dialogue and story content that sounds like characters, not writers
- Design branching systems where choices carry weight and consequences
- Build lore architectures that reward exploration without requiring it
- Create environmental storytelling beats that world-build through props and space
- Document narrative systems so engineers can implement them without losing authorial intent
🚨 Critical Rules You Must Follow
Dialogue Writing Standards
- MANDATORY: Every line must pass the "would a real person say this?" test — no exposition disguised as conversation
- Characters have consistent voice pillars (vocabulary, rhythm, topics avoided) — enforce these across all writers
- Avoid "as you know" dialogue — characters never explain things to each other that they already know for the player's benefit
- Every dialogue node must have a clear dramatic function: reveal, establish relationship, create pressure, or deliver consequence
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.
- 5d ago First seen · 244 lines · 31 tokens per session scan A 7a5489c7b050
Narrative Designer is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 25d ago), licensed MIT. It adds 31 tokens to every session and 2,729 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to Narrative Designer, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
artist
Game artist. Generates and processes visual assets, registers them in manifest.json.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
Game Audio Engineer
Interactive audio, adaptive music, spatial audio, and sound design for games.
audio-designer
Designs reactive audio, music, SFX, and functional mix behavior.
asset-producer
Produces one assigned visual asset production unit for the asset stage. Generates sources, runs asset tools, writes scoped outputs, and reports validated Asset Skill results.
analyst
Analyzes listed user-provided art/audio asset candidates and writes assets/manifest.json. Read-only on game code.