agentmods.dev

GhostWriterFramework AGENTS.md

A set of instructions for AI agents working on the Narrarium book-writing framework, where the repository is the source of truth for story facts and structure.

In plain words
What is it for?
Creating and updating characters, places, factions, items, secrets, timeline events, chapters, plot summaries, and release notes in a Narrarium project.
Why use it?
It reduces invented or contradictory story details by requiring agents to search existing canon and follow the project's update and versioning rules.

Instructions file for CodexOpenCode

0 5d ago A scan 960 tokens original MIT
View the source file KeyserDSoze/GhostWriterFramework
Install

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.

agentmods
npx agentmods add instructions/keyserdsoze/ghostwriterframework/agents-md
Clone the repo
git clone --depth 1 https://github.com/KeyserDSoze/GhostWriterFramework

Made for: Codex, OpenCode.

Per session 960 This file is loaded in full into every session.
When invoked 960 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00960 $0.00960
Opus 5 $0.00480 $0.00480
Sonnet 5 $0.00192 $0.00192
Haiku 4.5 $0.00096 $0.00096

Measured yesterday against content hash 1539d9660b08, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

GhostWriterFramework 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 yesterday.

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.

AGENTS.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Narrarium Agent Rules

Use Narrarium as a book-writing framework where the repository is the source of truth.

Default workflow

  1. Search canon before inventing new facts.
  2. Prefer Narrarium MCP tools over ad-hoc filesystem edits when creating or updating book structure.
  3. Use rich creation tools for major canon files:
    • create_character
    • create_location
    • create_faction
    • create_item
    • create_secret
    • create_timeline_event
  4. If the brief is incomplete, start a guided flow with:
    • start_wizard
    • wizard_answer
    • wizard_finalize
  5. After significant structural changes, refresh maintenance files:
    • sync_plot
    • sync_resume or sync_all_resumes
    • evaluate_chapter or evaluate_book

Narrarium MCP already auto-refreshes plot.md and the resume files after final chapter or paragraph mutations. Evaluations remain manual unless explicitly requested.

Versioning and patch notes

  • Every application change that is committed and pushed must bump src/narrarium-site/package.json and the root lockfile version according to the repository release workflow.
  • Before the version bump is committed, add a matching entry to src/narrarium-site/src/content/patch-notes.json.
  • Every patch-note entry must contain a title, summary, and non-empty change list in both English (en) and Italian (it).
  • Patch notes must describe user-visible behavior and navigation, not only internal implementation details.
  • Never commit or push a Narrarium site version without a matching bilingual patch note. npm run bms:build enforces this rule.
  • After each versioned commit, push main and monitor the Deploy Narrarium Site GitHub Actions workflow until completion, unless the user explicitly requests otherwise.

Canon discipline

  • Do not duplicate canon if the fact already exists in another markdown file.
  • Keep structured facts in frontmatter and prose in markdown body.
  • In chapter and scene prose, write character, item, location, faction, secret, and timeline-event names as plain text. Do not insert markdown links to canon files or reader routes; the reader will link visible canon mentions.
  • Do not reveal a secret before its known_from or reveal_in threshold.
  • Treat guidelines/, drafts/, plot.md, conversations/, resumes/, evaluations/, and secrets/ as first-class context, not optional notes.

Read the full file on GitHub · 73 lines

Changes

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.

  1. yesterday First seen · 73 lines · 960 tokens per session scan A 1539d9660b08

Subscribe to this mod's changes

GhostWriterFramework AGENTS.md is an instructions file published in the GitHub repository KeyserDSoze/GhostWriterFramework (0 stars, last pushed 5d ago), licensed MIT. It adds 960 tokens to every session, about $0.0048 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.

Git and workflowProductivityWriting and docs
Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens