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 egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine --skill studio-scalinggit clone --depth 1 https://github.com/egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-EngineWrote 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/egorfedorov/slot-casino-game-developer-skills-for-stake-engine/studio-scaling)<a href="https://agentmods.dev/skills/egorfedorov/slot-casino-game-developer-skills-for-stake-engine/studio-scaling"><img src="https://agentmods.dev/badge/skills/egorfedorov/slot-casino-game-developer-skills-for-stake-engine/studio-scaling/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/egorfedorov/slot-casino-game-developer-skills-for-stake-engine/studio-scaling"><img src="https://agentmods.dev/badge/skills/egorfedorov/slot-casino-game-developer-skills-for-stake-engine/studio-scaling.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.00043 | $0.00323 |
| Opus 5.5 | $0.00017 | $0.00129 |
| Sonnet 5.5 | $0.00009 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
studio-scaling 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
3 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.
- 2mo ago First seen · 52 lines · 43 tokens per session scan A 2ded4f928ef3
studio-scaling is a skill published in the GitHub repository egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine (82 stars, last pushed 8mo ago), with no licence file. It adds 43 tokens to every session and 323 once invoked, about $0.0002 per session on Opus 5.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
launch-checklist
Launch readiness across every department: code, content, store, marketing, community, infrastructure, legal, go/no-go sign-offs.
release-checklist
Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.
day-one-patch
Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.
milestone-review
Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation. At checkpoints or before a deadline.
team-combat
Orchestrate the combat team — game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, qa-tester — design through implement and validate.
team-live-ops
Orchestrate the live-ops team — live-ops-designer, economy-designer, analytics-engineer, community-manager, writer — for a season or live event.