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/lucadj77/tabletop-creator-plugin/ttc-variablesnpx skills add lucadj77/tabletop-creator-plugin --skill ttc-variablesgit clone --depth 1 https://github.com/lucadj77/tabletop-creator-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/lucadj77/tabletop-creator-plugin/ttc-variables)<a href="https://agentmods.dev/skills/lucadj77/tabletop-creator-plugin/ttc-variables"><img src="https://agentmods.dev/badge/skills/lucadj77/tabletop-creator-plugin/ttc-variables.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.00061 | $0.00506 |
| Opus 5 | $0.00030 | $0.00253 |
| Sonnet 5 | $0.00012 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
ttc-variables 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.
What it actually says
Create or edit TTC variables
Variables live in data/variables.json and are referenced as {code} inside panel and detail values.
First read ${CLAUDE_PLUGIN_ROOT}/docs/ttc-guidelines.md (all sections) and the variables section of ${CLAUDE_PLUGIN_ROOT}/docs/ttc-file-format.md.
Steps
- Validate the project folder; read
data/variables.jsonplus the blueprints/sets that use the affected tags (grep for{code}acrossdata/). Back up before modifying. - First check the tag is really meant to be a variable:
{tag}can also be a reference to a panel of the component (see "Tag resolution" in the file-format doc). If the tag matches a panel name, no variable is needed — and creating one would shadow the panel reference, since variables resolve first. Never create a variable whosecodeequals a panel name. - Each variable:
{"code": "...", "replacement": "...", "force_tint": "True"|"False"}with optional"color": "#RRGGBBAA"(typically#FFFFFF00whenforce_tintis"False").replacementmay contain plain text, other tags ({s1_ico}), or library icon ids (Category/name).- For variable families driven by composition (
{{panel}_suffix}), keep the naming scheme consistent (e.g.y1_s...y6_s) and cover every value the driving panel can take. "null"as replacement renders nothing — the idiom for optional/empty slots.
- When renaming a variable, update every
{oldcode}occurrence in blueprints and sets. When deleting, first show the user where it is still used. - Warn if the project exceeds 10 custom variables and the user may be on the free tier (free cap is 10).
- Validate (guidelines section 6): every tag referenced anywhere resolves; no orphaned family members. Remind the user to reload the project in TTC.
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 · 23 lines · 61 tokens per session scan A 25c35976a832
ttc-variables is a skill published in the GitHub repository lucadj77/tabletop-creator-plugin (2 stars, last pushed 11d ago), licensed MIT. It adds 61 tokens to every session and 506 once invoked, about $0.0003 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-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…
threejs-exposure-color-grading
Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.