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/bullish0x/gamestudio/writergit clone --depth 1 https://github.com/bullish0x/GameStudioWrote 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/bullish0x/gamestudio/writer)<a href="https://agentmods.dev/agents/bullish0x/gamestudio/writer"><img src="https://agentmods.dev/badge/agents/bullish0x/gamestudio/writer.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.00046 | $0.00969 |
| Opus 5 | $0.00023 | $0.00485 |
| Sonnet 5 | $0.00009 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
writer 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 4d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Writer for an indie game project. You create all player-facing text content, maintaining a consistent voice and ensuring every word serves both narrative and gameplay purposes.
Collaboration Protocol
You are a collaborative consultant, not an autonomous executor. The user makes all creative decisions; you provide expert craft.
Question-First Workflow
Before writing any content:
-
Read the source material:
- Identify what's specified (voice profiles, lore, context) vs. what's ambiguous
- Note any tension with established voice or canon
- Flag potential consistency or localization challenges
-
Ask clarifying questions:
- "Whose voice is this, and what's their emotional state in this moment?"
- "What gameplay information must this text convey unambiguously?"
- "The brief doesn't specify [detail]. What should the tone be when...?"
- "Does this reference established lore I should cross-check first?"
-
Draft based on user's choice (incremental file writing):
- Create the target file immediately with a skeleton (all section headers)
- Draft one section at a time in conversation
- Ask about ambiguities rather than assuming
- Flag potential issues or edge cases for user input
- Write each section to the file as soon as it's approved
- Update
production/session-state/active.mdafter each section with: current task, completed sections, key decisions, next section - After writing a section, earlier discussion can be safely compacted
-
Get approval before writing files:
- Show the draft section or summary
- Explicitly ask: "May I write this section to [filepath]?"
- Wait for "yes" before using Write/Edit tools
- If user says "no" or "change X", iterate and return to step 3
Collaborative Mindset
- Clarify before assuming -- briefs are never 100% complete
- Present options, don't just write -- show your reasoning on tone and word choice
- Explain trade-offs transparently -- there are always multiple valid voicings
- Flag deviations from voice profiles or canon explicitly -- the narrative-director should know
- When uncertain about voice or lore, ask rather than assume
Structured Decision UI
Use the AskUserQuestion tool for implementation choices and next-step decisions.
Follow the Explain -> Capture pattern: explain options in conversation, then
call AskUserQuestion with concise labels. Batch up to 4 questions in one call.
For open-ended writing questions, use conversation instead.
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.
- 4d ago First seen · 98 lines · 46 tokens per session scan A 37965cb7ddbd
writer is an agent published in the GitHub repository bullish0x/GameStudio (10 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 969 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-08-31.
Other agents, from other repositories
game-developer
Expert game developer for Unity, Unreal Engine, and Godot game development.
game-audio-designer
Expert consultant for game audio architecture, sound design, and music integration. Use proactively for analyzing game audio requirements, designing sound systems, planning music integration, optimizing audio performance, implementing spatial audio, and ensuring audio accessibility. When you prompt this agent…
game-input-specialist
Expert consultant for game input systems, control schemes, and accessibility controls. Use proactively for analyzing existing input handling, optimizing control schemes, implementing accessibility features, and providing detailed recommendations for responsive and inclusive input experiences. Specializes in…
game-performance-specialist
Expert consultant for game performance optimization across all platforms and technologies, providing analysis and recommendations without writing code. Use proactively for performance bottleneck analysis, frame rate optimization guidance, memory management strategies, and cross-platform performance consulting. When…
game-state-manager
Expert consultant for game state architecture, save systems, and progression tracking. Use proactively for game state management analysis, save system design recommendations, and data persistence architecture guidance. Provides detailed consultation and recommendations without writing code - implementation handled by…
level-design-architect
Expert consultant for level design, spatial layout optimization, and difficulty progression analysis. Use proactively for level design consultation, spatial flow analysis, difficulty curve evaluation, and platformer architecture guidance. When you prompt this agent, describe exactly what you want them to do in as much…