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 skills add rondorkerin/gamestack --skill worldbuilding-and-loregit clone --depth 1 https://github.com/rondorkerin/gamestackWrote 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/rondorkerin/gamestack/worldbuilding-and-lore)<a href="https://agentmods.dev/skills/rondorkerin/gamestack/worldbuilding-and-lore"><img src="https://agentmods.dev/badge/skills/rondorkerin/gamestack/worldbuilding-and-lore/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/rondorkerin/gamestack/worldbuilding-and-lore"><img src="https://agentmods.dev/badge/skills/rondorkerin/gamestack/worldbuilding-and-lore.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.00161 | $0.00911 |
| Opus 5 | $0.00081 | $0.00456 |
| Sonnet 5 | $0.00032 | $0.00182 |
| Haiku 4.5 | $0.00016 | $0.00091 |
Grade A, and why
worldbuilding-and-lore 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worldbuilding & Lore Delivery
How to author a deep, internally consistent world and deliver it through space and objects instead of exposition — and how to do that under procedural / AI generation without the world contradicting itself or collapsing into generic fantasy. The spine: build the whole iceberg as frozen, typed, queryable canon, then generate only the leaves that read from it.
When to use this
- Authoring the world bible (cosmology, timeline, factions, geography, economy, magic laws)
- Deciding how lore reaches the player (item text, environment, aftermath vs. cutscene/dialogue)
- Defining the world's identity/register so generation doesn't drift toward Tolkien defaults
- Designing mythology and "deep history" that the player can actually feel
- Making each mechanic carry the theme (ludonarrative harmony) and answer a lore question
- Diagnosing info-dumps, "wiki voice", generic-fantasy regression, or unbounded ambiguity
Scope
This skill owns the world bible and lore delivery. Adjacent concerns live in siblings:
- The space lore is delivered through →
open-world-design - How to generate content + the sameness problem →
procedural-generation,procgen-review - Keeping generated lore text coherent in voice →
ai-authored-content-coherence - Quests that carry lore →
narrative-and-quest-design - Visual register / readability of the alien look →
art-direction-and-readability - Mechanics whose lore you're justifying (loot, economy, death) →
rpg-systems,permadeath-and-lethality - "Interesting decisions" / ludonarrative theory →
game-design-fundamentals,systemic-emergent-design
How the pieces fit
GUIDE.md— the why: five sub-domains (iceberg, environmental/item delivery, alien-but-coherent identity, deep history, ludonarrative harmony), each with exemplars, citations, a "test for" criterion, a named failure mode, and the procedural/AI-authoring implication.CHECKLIST.md— the what to do: Do/Don't + Test-for, grouped by sub-domain.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 42 lines · 161 tokens per session scan A 651893a1c406
worldbuilding-and-lore is a skill published in the GitHub repository rondorkerin/gamestack (28 stars, last pushed 2mo ago), licensed MIT. It adds 161 tokens to every session and 911 once invoked, about $0.0008 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 skills, from other repositories
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
architecture-review
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL…
localize
Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.
vertical-slice
Pre-Production validation — build a production-quality end-to-end build to confirm the full game loop is achievable before committing to Production. Run after GDDs, architecture, and UX specs are complete. Produces a PROCEED/PIVOT/KILL verdict that gates the Pre-Production → Production transition.
quick-design
Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.
soak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.