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/commands/vstrapasson/rpg-marketplace/forge-compile)<a href="https://agentmods.dev/commands/vstrapasson/rpg-marketplace/forge-compile"><img src="https://agentmods.dev/badge/commands/vstrapasson/rpg-marketplace/forge-compile/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/commands/vstrapasson/rpg-marketplace/forge-compile"><img src="https://agentmods.dev/badge/commands/vstrapasson/rpg-marketplace/forge-compile.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.00029 | $0.00255 |
| Opus 5 | $0.00015 | $0.00128 |
| Sonnet 5 | $0.00006 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
forge-compile 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 8d 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.
What it actually says
/forge-compile
Compile the named sessao, encontro, or desafio into Foundry. This hands off to the rpg-forge-conductor skill — invoke it for <note name> and follow its playbook:
- Preflight (
/forge-preflightchecks) — stop on any critical fail. - Resolve the unit → entity graph (block on broken vault links).
- Plan (dry-run) — show the ordered build plan grouped by concern; get the user's approval before any write.
- Build per concern (scenes+lighting → actors+tokens → journals → encounters → challenges → ownership), serializing scene writes, updating the build manifest after each step.
- Verify against live Foundry.
- Review — spawn
rpg-foundry-reviewerand relay findings.
Always confirm before: generating a map (ComfyUI job) and assigning player ownership. Re-running is safe (idempotent via the manifest).
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.
- 8d ago First seen · 17 lines · 29 tokens per session scan A dc2a5f2af0c7
forge-compile is a command published in the GitHub repository vstrapasson/rpg-marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 255 once invoked, about $0.0001 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 commands, from other repositories
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
status
Show 3d-design team status and recent activity.
unity-optimize
Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.