agentmods.dev

sts2-prepare-runtime

sts2-prepare-runtime is a skill for Claude Code, Codex from ttxttx1111/sts2-llm. It costs 40 tokens per session (1,098 once invoked), scanned A, original, MIT.

A setup checklist for controlling Slay the Spire 2 through an MCP connection, a way for an agent to call game-control tools. It checks that the current session can read the game's state before play begins.

In plain words
What is it for?
Use it to prepare a Copilot CLI or agent session for live Slay the Spire 2 play and verify that the game-state tool works.
Why use it?
It prevents a play session from starting when the required game connection or controls are missing. It also explains whether the setup lasts only for the current session or future sessions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 41 1mo ago A scan 40 tokens original MIT
View the source file ttxttx1111/sts2-llm
Install

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.

agentmods
npx agentmods add skills/ttxttx1111/sts2-llm/sts2-prepare-runtime
Any agent
npx skills add ttxttx1111/sts2-llm --skill sts2-prepare-runtime
Clone the repo
git clone --depth 1 https://github.com/ttxttx1111/sts2-llm

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for sts2-prepare-runtime

README.md
[![agentmods](https://agentmods.dev/badge/skills/ttxttx1111/sts2-llm/sts2-prepare-runtime.svg)](https://agentmods.dev/skills/ttxttx1111/sts2-llm/sts2-prepare-runtime)
Your own site
<a href="https://agentmods.dev/skills/ttxttx1111/sts2-llm/sts2-prepare-runtime"><img src="https://agentmods.dev/badge/skills/ttxttx1111/sts2-llm/sts2-prepare-runtime.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,098 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01098
Opus 5 $0.00020 $0.00549
Sonnet 5 $0.00008 $0.00220
Haiku 4.5 $0.00004 $0.00110

Measured 6d ago against content hash d706c547c20e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

sts2-prepare-runtime 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 6d 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.

.github/skills/sts2-prepare-runtime/SKILL.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

STS2 runtime preparation workflow

Use this skill when the task is to make the current session ready for live STS2 control.

What this skill owns

  • checking whether STS2 MCP tools are already attached to the current session
  • accepting a working current-session MCP attachment, even if it is only temporary
  • explaining or restoring the MCP setup needed for a fresh Copilot CLI session or /agent launch
  • verifying that the runtime can actually call get_game_state
  • handing off to sts2-pilot-run only after the session is ready

Operating loop

  1. Check whether STS2 MCP is already available

    • confirm the current session exposes get_game_state
    • if available, also verify that menu / combat control tools expected by the current task are present
    • if the tools are present, treat the runtime as ready and hand off to sts2-pilot-run, whether the attachment came from a temporary session-level MCP add or a persistent startup config

  2. If MCP is missing, diagnose the likely class of blocker

    • a fresh session or /agent launch did not inherit a prior session's MCP attachment
    • the user may still prefer a temporary attachment for the current live session because it is simpler or faster
    • Copilot CLI does not yet have a persistent STS2 MCP config
    • the game or mod is not running even though the server config exists
    • when filesystem access is available, prefer to repair or create the persistent CLI MCP config directly instead of stopping at instructions for the user

  3. Choose the lightest setup that matches the goal

    • if the current session already has STS2 MCP tools attached, do not block play just because the setup is not persistent
    • if the user wants to keep playing in the current conversation, a temporary session-level MCP attachment is acceptable and often the fastest option
    • if the goal is to close the main session and later open a new session or custom agent directly, do not rely on another session's runtime state
    • for that cross-session case, ensure Copilot CLI has a persistent MCP configuration available at session start, using /mcp add or ~/.copilot/mcp-config.json
    • the shared VS Code repo reference lives in ../../../.vscode/mcp.json and uses the VS Code-style servers key
    • Copilot CLI home config uses mcpServers instead
    • the current repo reference is:

Read the full file on GitHub · 101 lines

Changes

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.

  1. 6d ago First seen · 101 lines · 40 tokens per session scan A d706c547c20e

Subscribe to this mod's changes

sts2-prepare-runtime is a skill published in the GitHub repository ttxttx1111/sts2-llm (41 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,098 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.

Game developmentai-agentcopilot-cligithub-copilotmcpslay-the-spire-2sts2
Related

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…

microsoft/Build-CLI · 109 tokens

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…

github/spec-kit-copilot · 113 tokens

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…

github/spec-kit-copilot · 99 tokens

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…

github/spec-kit-copilot · 88 tokens

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…

github/spec-kit-copilot · 83 tokens

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…

github/spec-kit-copilot · 93 tokens