Borrowing it
Nothing to install: this file belongs to geleynse/gantry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/geleynse/gantry/main/.claude/skills/prayerlang/SKILL.mdgit clone --depth 1 https://github.com/geleynse/gantryWrote 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/geleynse/gantry/prayerlang)<a href="https://agentmods.dev/skills/geleynse/gantry/prayerlang"><img src="https://agentmods.dev/badge/skills/geleynse/gantry/prayerlang.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.1 | $0.00065 | $0.03688 |
| Opus 5 | $0.00032 | $0.01844 |
| Sonnet 5 | $0.00013 | $0.00738 |
| Haiku 4.5 | $0.00006 | $0.00369 |
Grade A, and why
prayerlang 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 7d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PrayerLang
PrayerLang is a tiny DSL that lets a fleet agent submit one bounded,
deterministic script to the server instead of driving a mining/trading loop
turn-by-turn — one spacemolt_pray MCP call replaces N LLM turns. The runtime
parses, statically analyzes (arity, denied tools, fuzzy item/POI resolution),
then executes server-side against the agent's cached game state, dispatching
real game tool calls as it goes. Inspired by
prayer.rs; Gantry's version
is a from-scratch TypeScript reimplementation for the SpaceMolt tool surface.
Where it lives
All in server/src/proxy/prayer/, each file with a co-located *.test.ts:
| File | Role |
|---|---|
parser.ts |
Lexer + recursive-descent parser. parsePrayerScript(source) → AstProgram; formatPrayerProgram() is the canonical pretty-printer used for normalized_script. |
analyzer.ts |
Static pass: resolves command/predicate specs, checks arity, fuzzy-matches item/POI identifiers (Levenshtein), checks agentDeniedTools. analyzePrayerProgram(ast, snapshot) → AnalyzedProgram. |
executor.ts |
Runs the analyzed program statement-by-statement; owns step/loop/wall-clock limits and mid-script interrupt checks. executePrayerProgram(program, deps) → PrayResult. |
commands.ts |
COMMANDS registry (one CommandSpec per statement keyword) + UNSUPPORTED_COMMANDS deny-list. |
predicates.ts |
evalPredicate() + computeMetric() — the if/until condition evaluator. |
state.ts |
Pure readers over the cached status blob (getCargo, cargoPct, homeDestination, ...) — every predicate/command reads through these, never data.foo directly. |
checkpoint.ts |
Serialize/persist/resume ExecState across server restarts. |
result.ts |
Builds the final PrayResult: diff snapshot + tiered error shape. |
index.ts |
runPrayerScript(script, deps) — public entry point: parse → analyze → execute, catching errors from any stage into resultFromError. |
types.ts |
All shared types: AST, CommandSpec, PredicateName, ExecState, PrayResult, the three error classes. |
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.
- 7d ago First seen · 223 lines · 65 tokens per session scan A 3bd5db763af0
prayerlang is a skill published in the GitHub repository geleynse/gantry (3 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 3,688 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-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.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.