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 skills add ttxttx1111/sts2-llm --skill sts2-pilot-rungit clone --depth 1 https://github.com/ttxttx1111/sts2-llmWrote 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/ttxttx1111/sts2-llm/sts2-pilot-run)<a href="https://agentmods.dev/skills/ttxttx1111/sts2-llm/sts2-pilot-run"><img src="https://agentmods.dev/badge/skills/ttxttx1111/sts2-llm/sts2-pilot-run/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/skills/ttxttx1111/sts2-llm/sts2-pilot-run"><img src="https://agentmods.dev/badge/skills/ttxttx1111/sts2-llm/sts2-pilot-run.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.00047 | $0.01555 |
| Opus 5 | $0.00023 | $0.00777 |
| Sonnet 5 | $0.00009 | $0.00311 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
sts2-pilot-run 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 9d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STS2 pilot run workflow
Use this skill when the task is to play the run in front of you.
What this skill owns
- reading the current game state
- deciding combat turns
- choosing card rewards, routes, shop buys, and rest actions
- refreshing run memory before major decisions
- updating the current-run playbook after meaningful pivots
- updating the active run timeline so recent-run status is queryable later
Operating loop
-
Start with
get_game_state- prefer
format: "json"in combat - prefer
format: "markdown"for map, event, reward, shop, and rest screens
- prefer
-
Refresh memory before non-trivial decisions
- read the current playbook at ../../sts2-memory/current-playbook.md
- read the lesson ledger at ../../sts2-memory/lesson-ledger.md
- briefly state which 1 to 3 lessons still apply
- in the first meaningful draft, path, shop, and rest decisions of a new run after a loss, also recall the last deck autopsy and name which prior failure mode this line is fixing or risking
- do not load the full review archive during live play unless the current choice depends on a rare card, relic, event, boss, or another narrow situation that the compressed memory does not cover well
- if none apply, say so explicitly
-
Choose the line that best improves current win rate
- combat: balance survival, tempo, kill pressure, and next-turn risk
- rewards: improve deck quality, not deck size for its own sake
- route: balance HP, elites, shops, upgrades, and map flexibility
- events, rests, shops: weigh long-term gain against immediate danger
- for card rewards, shops, and card-related campfire choices, structure the decision as:
这张牌是哪类 -> 这把缺哪类 -> 这次拿/跳 -> 拿了以后还要补什么 - default card buckets are
前期战力牌 / 结构胶水牌 / 体系成长牌 - do not let a strong Act 1 frontload pickup masquerade as proof that scaling, access, premium block, or post-burst floor are already solved
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.
- 9d ago First seen · 87 lines · 47 tokens per session scan A 98fa8b65687e
sts2-pilot-run is a skill published in the GitHub repository ttxttx1111/sts2-llm (41 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,555 once invoked, about $0.0002 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
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
speckit-init
Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running specify init --integration copilot --integration-options="--skills". USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO…
speckit-bundle
Discover, install, and author Spec Kit bundles via specify bundle. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and…
speckit-extension
Manage Spec Kit extensions via specify extension. USE FOR: installing/removing/updating spec-kit extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting extension resolution priority, managing extension catalogs. DO NOT USE FOR: presets (use speckit-preset), bundles…
speckit-preset
Manage Spec Kit presets via specify preset. USE FOR: installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting preset resolution priority, managing preset catalogs. DO NOT USE FOR: extensions (use…
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…