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 agentmods add skills/cyface/foundryvtt-dev-claude-plugin/foundryvtt-systemnpx skills add cyface/foundryvtt-dev-claude-plugin --skill foundryvtt-systemgit clone --depth 1 https://github.com/cyface/foundryvtt-dev-claude-pluginWrote 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/cyface/foundryvtt-dev-claude-plugin/foundryvtt-system)<a href="https://agentmods.dev/skills/cyface/foundryvtt-dev-claude-plugin/foundryvtt-system"><img src="https://agentmods.dev/badge/skills/cyface/foundryvtt-dev-claude-plugin/foundryvtt-system.svg" alt="Measured on agentmods" 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 | $0.00208 | $0.02901 |
| Opus 5 | $0.00104 | $0.01451 |
| Sonnet 5 | $0.00042 | $0.00580 |
| Haiku 4.5 | $0.00021 | $0.00290 |
Grade A, and why
foundryvtt-system 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 4d 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FoundryVTT System Development Guide
This guide covers the fundamentals of building a game system or module for FoundryVTT v13. It provides patterns for project structure, data models, hooks, documents, settings, testing, and internationalization.
Note: This plugin is a community resource and is not affiliated with or endorsed by Foundry Gaming LLC.
System File Structure
A typical FoundryVTT system:
my-system/
+-- module/ # JavaScript source
| +-- __tests__/ # Test files (Vitest)
| +-- __mocks__/ # Test mocks for Foundry API
| +-- my-system.js # Entry point (registered in system.json)
| +-- actor.js # Custom Actor class
| +-- item.js # Custom Item class
| +-- config.js # System constants and lookup tables
| +-- ...
+-- templates/ # Handlebars templates (.html)
+-- styles/ # SCSS/CSS stylesheets
+-- lang/ # Translation files (en.json, de.json, etc.)
+-- packs/ # Compendium packs
| +-- creatures/
| | +-- src/ # JSON source files (tracked in git)
| +-- items/
| +-- src/
+-- docs/ # Documentation
+-- system.json # System manifest
+-- template.json # Data model definition
Data Model (template.json)
Defines the structure of Actor and Item data:
{
"Actor": {
"types": ["character", "npc"],
"character": {
"hp": { "value": 10, "max": 10 },
"level": 1,
"abilities": {
"str": { "value": 10 },
"dex": { "value": 10 },
"con": { "value": 10 },
"int": { "value": 10 },
"wis": { "value": 10 },
"cha": { "value": 10 }
},
"biography": ""
},
"npc": {
"hp": { "value": 10, "max": 10 },
"cr": 1,
"description": ""
}
},
"Item": {
"types": ["weapon", "armor", "spell", "equipment"],
"weapon": {
"damage": "1d6",
"attackBonus": 0,
"equipped": false
},
"armor": {
"ac": 10,
"equipped": false
},
"spell": {
"level": 1,
"description": ""
},
"equipment": {
"quantity": 1,
"weight": 0,
"description": ""
}
}
}
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.
- 4d ago First seen · 418 lines · 208 tokens per session scan A 8e96be5cef91
foundryvtt-system is a skill published in the GitHub repository cyface/foundryvtt-dev-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 208 tokens to every session and 2,901 once invoked, about $0.0010 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 skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…