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/tlaplus/agentskills/tlaplus-add-variablenpx skills add tlaplus/AgentSkills --skill tlaplus-add-variablegit clone --depth 1 https://github.com/tlaplus/AgentSkillsWhat 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.00069 | $0.01111 |
| Opus 5 | $0.00034 | $0.00556 |
| Sonnet 5 | $0.00014 | $0.00222 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
tlaplus-add-variable 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 2d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Variable to TLA+ Specification
Add a new variable to a TLA+ specification while preserving semantics. The new variable must appear in all necessary locations so the specification remains valid and its behavior is unchanged.
Required Locations for New Variables
When adding a variable newVar to a TLA+ specification, update these locations:
- VARIABLE declaration block - Add the variable name
- Init - Initialize the variable
- All UNCHANGED statements - Add variable to every UNCHANGED that doesn't modify it
- vars tuple - Add to the tuple used in temporal formulas (if exists)
- TypeOk (optional) - Add type constraint if TypeOk invariant exists
Workflow
Step 1: Analyze the Specification
Read the TLA+ file and identify:
- All existing variables in the VARIABLE block
- The Init predicate
- All actions and their UNCHANGED statements
- The
varstuple or similardefinition (usually near Next or Spec) - TypeOk invariant if present
Step 2: Add Variable Declaration
Add the new variable to the VARIABLE block. Preserve formatting:
VARIABLE
existingVar1,
existingVar2,
newVar \* Add with comment explaining purpose
Step 3: Initialize in Init
Add initialization. Match the style of existing initializations:
Init ==
/\ existingVar1 = ...
/\ existingVar2 = ...
/\ newVar = <initial_value>
Step 4: Update All UNCHANGED Statements
Critical step. Find every UNCHANGED statement and add the new variable:
\* Before:
UNCHANGED << existingVar1, existingVar2 >>
\* After:
UNCHANGED << existingVar1, existingVar2, newVar >>
Search patterns to find UNCHANGED statements:
UNCHANGED <<- tuple formUNCHANGEDfollowed by variable name - single variable form
For single-variable UNCHANGED, convert to tuple form:
\* Before:
UNCHANGED existingVar
\* After:
UNCHANGED << existingVar, newVar >>
Step 5: Update vars Tuple
If a vars tuple exists, add the new variable:
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.
- 2d ago First seen · 189 lines · 69 tokens per session scan A 7c07a610d6f9
tlaplus-add-variable is a skill published in the GitHub repository tlaplus/AgentSkills (36 stars, last pushed 7mo ago), licensed MIT. It adds 69 tokens to every session and 1,111 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-30.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.