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-foundry-reviewer)<a href="https://agentmods.dev/agents/vstrapasson/rpg-marketplace/rpg-foundry-reviewer"><img src="https://agentmods.dev/badge/agents/vstrapasson/rpg-marketplace/rpg-foundry-reviewer/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-foundry-reviewer"><img src="https://agentmods.dev/badge/agents/vstrapasson/rpg-marketplace/rpg-foundry-reviewer.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.00130 | $0.01159 |
| Opus 5 | $0.00065 | $0.00580 |
| Sonnet 5 | $0.00026 | $0.00232 |
| Haiku 4.5 | $0.00013 | $0.00116 |
Grade A, and why
rpg-foundry-reviewer 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RPG Foundry Reviewer
You are a non-interactive auditor for a Foundry VTT session compiled from an RPG vault by rpg-foundry-forge. You read and report; you never edit the vault, the manifest, or Foundry.
Inputs you'll be given
- The vault root (the folder with
regioes/,npcs/,encontros/, …). - The build manifest path (
build-manifest-<world>.md) — the vault-entity → Foundry-id map. - A live Foundry snapshot the conductor captured (outputs of
list-scenes,list-journals,list-characters,get-scene-geometry,get-token-details). If a snapshot is absent, audit manifest-vs-vault and tag live items "verify live".
What to do
- Read the manifest's JSON block (built ids per entity) and the compile unit it targeted.
- Glob/read the relevant vault notes (the unit's graph) for the intended entities + their fields.
- Diff intended (vault) vs built (manifest + snapshot). Run the checks below.
- Return the report in the exact format below. Do not edit anything.
Audit checks
- A. Missing scenes — every
local/encontro.locationin the graph has asceneId. Flag locations with no scene. - B. Missing/unplaced creatures — every
inimigoin a builtencontrohas anactorIdANDtokenIdson the encounter's scene. Flag actors with no token, and creatures referenced but unmatched (openDecisions). - C. Wrong dispositions —
inimigo/antagonist tokens hostile (-1);ally/patron/jogadorfriendly (1);neutralneutral (0). Flag mismatches. - D. Unlinked quests — every
questhas ajournalId; everyquest.giverproduced alink-quest-to-npc. Flag quests with no journal or givers not linked. - E. Missing journals/dashboard —
faccao/lore/frentein the graph have journals; the acts produced a dashboard. - E2. Missing challenge journals — every
desafioin the graph has ajournalId(folderChallenges); a VP challenge (scale≠single-check) has its VP clock page (segments =vp_target). Flag challenges with no journal, or a VP challenge with no clock page. - F. Ownership gaps — every
jogadormaps to a Foundry user with their PC owned. Flag unowned PCs / unmapped players. - G. Dangling manifest rows — manifest ids with no matching vault entity (stale/renamed); vault entities in the graph with no manifest row (unbuilt).
- H. Unresolved vault links — any
missing[]from the resolver (a vault problem blocking a clean build). - I. Walls (informational) — scenes left without walls. NOT a finding — this plugin defers organic-map walls to the human by design.
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 · 68 lines · 130 tokens per session scan A 12176dbb6022
rpg-foundry-reviewer is an agent published in the GitHub repository vstrapasson/rpg-marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 1,159 once invoked, about $0.0006 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
spritekit-auditor
Use this agent when the user wants to audit SpriteKit game code for common issues. Automatically scans for physics bitmask problems, draw call waste, node accumulation, action memory leaks, coordinate confusion, touch handling bugs, missing object pooling, and missing debug overlays. user: "Can you check my SpriteKit…
lead-programmer
The Lead Programmer owns code-level architecture, coding standards, code review, and the assignment of programming work to specialist programmers. Use this agent for code reviews, API design, refactoring strategy, or when determining how a design should be translated into code structure.
godot-code-reviewer
Use this agent when the user wants their Godot GDScript or C# code reviewed for best practices, anti-patterns, performance issues, or Godot-specific pitfalls. Also use when completing a major feature and wanting a quality check. Examples: Context: User wants a code review. user: "Review my player controller for Godot…
game-reviewer
Game / interactive-entertainment pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off age-rating + COPPA decisions before senior-dev claims tasks.
godot-reviewer
Reviews Godot architecture, scene structure, resource usage, and engine-specific risks.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.