Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/serejaris/kimi-skillsnpx agentmods add skills/serejaris/kimi-skills/game-writingWrote 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/serejaris/kimi-skills/game-writing)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/game-writing"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/game-writing/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/serejaris/kimi-skills/game-writing"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/game-writing.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.00046 | $0.04546 |
| Opus 5 | $0.00023 | $0.02273 |
| Sonnet 5 | $0.00009 | $0.00909 |
| Haiku 4.5 | $0.00005 | $0.00455 |
Grade A, and why
game-writing 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 9d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game Writing
Sub-skill of general-writing. Inherits shared principles, anti-AI discipline, and quality gates.
CRITICAL — Review → Fix Brief → Dispatched Subagent: When a review finds issues, translate them into a detailed fix brief (file paths, quoted findings, expected outcome, scope boundary, self-check) and dispatch a fresh subagent to apply the fix. Never use inline sed/edit_file fixes.
CRITICAL — Anti-Read-Loop Rule: The orchestrator must dispatch its first subagent (world_planner or detail_planner) within 10 iterations. If the orchestrator has spent 10+ iterations only reading files without creating any subagent, it is in a read-loop. Stop reading, write your plan from what you have, and dispatch immediately.
CRITICAL — Step Budget & Delivery: You have a limited step budget. Plan delivery accordingly:
- Small projects (1-2 deliverable types): fully achievable in one session.
- Large projects (full world bible + quests + dialogues + flavor): prioritize world bible and highest-priority deliverables. Deliver completed deliverables with .docx and ask user whether to continue with remaining types.
- Before your session ends: always assemble completed deliverables and convert to .docx.
CRITICAL — .docx Delivery: Every completed assembly must be converted to .docx using
skills/docx/SKILL.md. Never end a session with raw .md files and no .docx deliverable.
Trigger Keywords
游戏文案, 游戏剧情, 游戏叙事, game narrative, game writing, quest design, dialogue tree, 世界观设定, 角色设定, character bible, lore, item description, barks, 技能描述, flavor text, 战斗系统, combat system, 数值策划, progression, gacha, 副本设计
File Paths
Output Directory Structure
/mnt/agents/output/
├── research/ # User uploads (game design docs, lore bibles)
├── {project_name}.outline.md
├── documents/
│ ├── {project_name}.world_bible.md
│ ├── {project_name}.characters.md
│ └── {project_name}.quest_registry.md
└── deliverables/
├── characters/
├── quests/
├── dialogues/
└── flavor_text/
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.
- 9d ago First seen · 306 lines · 46 tokens per session scan A ab8b92e8a687
game-writing is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 4,546 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-03.
Other skills, from other repositories
story-commentary-workflow
A specialized Agent Skill for organizing game story footage, planning story commentary videos, splitting chapters, transcribing subtitles, drafting narration, and matching narration to visuals. Use when the user mentions story commentary, game plot recaps, story condensation, chapter breakdowns, narration scripts…
story-worldbuilding-planner
Use this skill when the user wants to create or refine game stories, Chinese web novel plots, light novel plots, character arcs, faction settings, power systems, worldbuilding, lore bibles, chapter outlines, quest lines, or narrative design documents.
offensive-bluetooth-classic
Bluetooth Classic (BR/EDR) attack methodology — device discovery, service enumeration via SDP, LMP/L2CAP layer attacks, legacy PIN cracking (BlueBorne / KNOB), Bluetooth file-transfer abuse (BlueSnarfing legacy), unauthenticated profile abuse (HSP, HFP, OPP), and modern relevance against older industrial / automotive…
review-plan
Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
design-md-validator
Validate DESIGN.md files against the official Google specification using the @google/design.md CLI linter. Works with local files. Use when the user wants to lint a DESIGN.md, check spec compliance, find broken token references, verify WCAG contrast ratios, diff two versions, export tokens to Tailwind or DTCG format…