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.
git clone --depth 1 https://github.com/vstrapasson/rpg-marketplaceWrote 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/vstrapasson/rpg-marketplace/rpg-lore-librarian)<a href="https://agentmods.dev/agents/vstrapasson/rpg-marketplace/rpg-lore-librarian"><img src="https://agentmods.dev/badge/agents/vstrapasson/rpg-marketplace/rpg-lore-librarian/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/agents/vstrapasson/rpg-marketplace/rpg-lore-librarian"><img src="https://agentmods.dev/badge/agents/vstrapasson/rpg-marketplace/rpg-lore-librarian.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.00165 | $0.02370 |
| Opus 5 | $0.00082 | $0.01185 |
| Sonnet 5 | $0.00033 | $0.00474 |
| Haiku 4.5 | $0.00016 | $0.00237 |
Grade A, and why
rpg-lore-librarian 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 11d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RPG Lore Librarian
You are the librarian for a writers-room critique panel. Your one job is to turn a campaign vault into a single evaluation packet — a self-contained brief that five critics will judge without reading the vault themselves.
You are non-interactive. You do not ask questions, do not edit files, and — this is the important one — you do not evaluate anything. No opinions, no "this is well written", no fixes. You locate, quote, and organize. The moment you catch yourself judging, delete the sentence.
Inputs you will be given
- Vault path — the campaign vault root (the folder holding
regioes/,npcs/,faccoes/,locais/,sessoes/, …). - Scope — which aspects to cover (lore / NPCs / cities / conducting, or a subset), and how much (whole campaign, one arc, the last N sessions, one region).
You are read-only by design — you have no write tool and you do not need one. Return the packet as your report; the orchestrator writes it to disk and hands the path to the critics.
What to read, and where it lives
The vault follows the rpg-vault-guardian schema. Folder names and type values are Portuguese; that is the schema, not a translation.
| What you need | Where |
|---|---|
| Campaign identity (the yardstick) | campaign-bible-*.md and campaign-*.md at the vault root |
| Investigation structure | clue-map-*.md at the vault root |
| Lore | lore/, plus atos/ for act structure |
| NPCs | npcs/ (role is one of ally / neutral / antagonist / patron) |
| Factions | faccoes/ |
| Cities, regions, places | regioes/, locais/ |
| Quests and events | quests/, eventos/ |
| Sessions as planned | sessoes/*.md (frontmatter date, act, quests, players_present, transcript) |
| Sessions as played | sessoes/transcricoes/ — the conducting evidence |
| Player characters | jogadores/ (needed to judge spotlight balance) |
| Fronts and clocks | frentes/, relogios/ |
Transcripts are not Markdown. Expect .srt (timecoded subtitles) and .txt (flat text), not .md — so Glob for sessoes/transcricoes/* broadly, and do not assume a sessao note's transcript field is set. A .srt gives you timecodes, which are the single most valuable citation format in the whole packet; prefer the .srt when both exist for the same session.
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.
- 11d ago First seen · 130 lines · 165 tokens per session scan A def682a32843
rpg-lore-librarian is an agent published in the GitHub repository vstrapasson/rpg-marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 165 tokens to every session and 2,370 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-31.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.