Borrowing it
Nothing to install: this file belongs to zenstory-ai/novel-to-game. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zenstory-ai/novel-to-game/main/AGENTS.mdgit clone --depth 1 https://github.com/zenstory-ai/novel-to-gameWrote 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/instructions/zenstory-ai/novel-to-game/agents-md)<a href="https://agentmods.dev/instructions/zenstory-ai/novel-to-game/agents-md"><img src="https://agentmods.dev/badge/instructions/zenstory-ai/novel-to-game/agents-md/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/instructions/zenstory-ai/novel-to-game/agents-md"><img src="https://agentmods.dev/badge/instructions/zenstory-ai/novel-to-game/agents-md.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.00580 | $0.00580 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
novel-to-game AGENTS.md 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 12d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NovelToGame Engineering Guide
NovelToGame is a skills-first repository. Its product is adaptation judgment and reusable workflow knowledge, not a bundled game engine.
Rules
- Assume frontier models already know mainstream game and frontend frameworks.
- Treat game concept, experience/level design, and art direction as separate planning owners; do not let implementation silently redesign them.
- Add instructions only when they encode adaptation know-how, a necessary handoff contract, or evidence-based QA.
- Keep
SKILL.mdprocedural and concise. Put optional depth in one-levelreferences/files. - Keep every skill self-contained. Do not create runtime cross-skill file dependencies; invoke another skill by name instead.
- Do not bind the core design artifacts to Kimi, Claude, or one framework.
- Keep provider comparisons out of runtime skills; model capabilities change.
- Language scope is bounded per surface, not global:
- Skill bodies and
references/: Simplified Chinese, always. This is prose the agent reads at runtime; keeping it in one language avoids a bilingual layer that would have to be kept in sync through every contract refactor. - Frontmatter
description, the four plugin manifests, andagents/openai.yamlinterface fields: English first, Chinese after. These are what an agent routes an English request against and what a plugin directory shows as listing copy with no README fallback.scripts/validate_repo.pyenforces the English-first rule. - Examples: each example declares its own artifact language in its
example.json, and its planning artifacts, source provenance and in-game UI text follow that declaration.tests/test_validate_repo.pyonly requires Chinese headings for examples that declare azh*language. - README:
README.mdEnglish (the default),README_ZH.mdChinese, both kept structurally identical.
- Skill bodies and
- Treat repository language and generated-project language separately. Accept novels in any language; generated artifacts follow the user's requested language, or the conversation language when unspecified. Do not duplicate every artifact bilingually unless requested.
- Preserve source-language quotations and culturally specific concepts. When source and output languages differ, translate only what decisions require and keep one terminology table instead of flattening concepts into foreign tropes.
- Require evidence for QA claims: command output, state snapshots, screenshots, or recorded play paths.
- Do not describe subjective fun or balance as deterministically verified.
- Do not add dependencies without an explicit product need.
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.
- 12d ago First seen · 53 lines · 580 tokens per session scan A e61bd0e30aef
novel-to-game AGENTS.md is an instructions file published in the GitHub repository zenstory-ai/novel-to-game (775 stars, last pushed today), licensed MIT. It adds 580 tokens to every session, about $0.0029 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).