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 jeremylongworth-source/AgentSkills --skill game-skill-orchestrationgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/game-skill-orchestration)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/game-skill-orchestration"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/game-skill-orchestration/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/jeremylongworth-source/agentskills/game-skill-orchestration"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/game-skill-orchestration.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.00089 | $0.01604 |
| Opus 5.5 | $0.00036 | $0.00642 |
| Sonnet 5.5 | $0.00018 | $0.00321 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
game-skill-orchestration 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game Skill Orchestration
Core Workflow
- Classify the request by outcome, not by keywords alone: prototype, production feature, design doc, creative direction, review, refactor, asset plan, implementation, validation, or pitch.
- Select the smallest useful set of game skills. Combine skills only when the work genuinely crosses discipline boundaries.
- Write an outcome-first brief before detailed work when the task is broad:
- Desired player experience
- Concrete deliverable
- Target platform/engine
- Constraints and allowed side effects
- Acceptance criteria
- Evidence or validation required
- Open questions that materially affect the outcome
- Route domain work to the relevant skill references, then synthesize decisions into one coherent plan or artifact.
- Define validation depth based on risk: concept sanity check, checklist review, prototype test, playtest script, technical test, performance check, accessibility review, or production-readiness review.
- Keep outputs compact and structured. Use tables, checklists, and short specs when they make decisions easier to compare.
Cross-Skill Support
- Use
product-brainstorming-planningbefore this skill when the game idea is vague, exploratory, or not yet ready for a feature brief. - Use
game-playtesting-usabilitywhen design decisions need player evidence, usability findings, difficulty feedback, onboarding clarity, or playtest reports. - Use
experiment-design-validationwhen a game feature, onboarding change, monetization idea, or retention hypothesis should be tested before broad rollout. - Use
customer-research-validationwhen a game audience, player motivation, or demand assumption needs structured research. - Use
competitive-market-researchwhen genre, competitor, pricing, Steam/itch page, feature, or market-positioning evidence should inform decisions. - Use
accessibility-inclusive-designwhen game UI, controls, subtitles, motion, difficulty assists, remapping, or inclusive play needs accessibility review. - Use
pricing-packaging-strategywhen monetization, DLC, tiers, subscriptions, donations, pay-what-you-want, or storefront pricing needs structured pricing decisions. - Use
product-analytics-instrumentationwhen game telemetry, funnels, onboarding/retention metrics, playtest instrumentation, event taxonomy, or analytics QA is needed. - Use
qa-test-strategywhen game release quality, regression coverage, platform/device coverage, compatibility, or acceptance gates need structure. - Use
release-launch-readinesswhen publishing, launch, rollout, rollback, support, monitoring, or post-launch review needs coordination. - Use
visual-ui-ux-auditwithgame-ui-design,game-threejs-development, orgame-phaser-developmentwhen browser screenshots or interactive states should drive critique. - Use
react-next-performance-optimizationwhen a web-based game shell, landing page, editor, dashboard, or launcher uses React/Next.js. - Use
concise-technical-writingfor compact game design docs, changelogs, release notes, itch.io page copy, PR summaries, and implementation summaries. - Use
skill-evaluation-iterationwhen improving the game skillset itself or testing whether a game skill changes output quality.
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.
- 1mo ago First seen · 90 lines · 89 tokens per session scan A 96c46518d641
game-skill-orchestration is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 89 tokens to every session and 1,604 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
unity-yaml-format
Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
i4h-workflow-train-rl
Use when training, evaluating, or exporting Workflow policies with online RSL-RL or RLinf, including RL checkpoint and Workflow handoff.
cdf-autonomous-vehicle-dataset-generation
Prepare payloads, run and monitor the Autonomous Vehicle Dataset Generation Airflow workflow, and inspect results for driving-clip retrieval and Cosmos3-Nano variants. Existing clips with no retrieval use cdf-video-data-augmentation; seed-image event or anomaly generation uses cdf-event-video-generation.
unreal-cpp-architecture
Use when writing Unreal Engine 5 C++ - the gameplay framework classes and where logic belongs, UObject/AActor/UActorComponent lifecycle, UPROPERTY/UFUNCTION and GC-safe pointers (TObjectPtr, TWeakObjectPtr), subsystems, the C++/Blueprint boundary, Enhanced Input, tick discipline, and compiling from the command line.
bevy-ecs-patterns
Use when writing Bevy (Rust ECS) game code - pin and respect the repo's minor version, plugins/systems/queries/resources, schedules with FixedUpdate and Time, states and run conditions, messages vs observers across versions, required components, testing systems with App::update and a manual time strategy, compile-time…
game-loop-and-time
Use when writing anything that moves, animates, counts down or simulates - per-frame vs fixed-step callbacks per engine, the accumulator loop with interpolation, delta-scaled smoothing, pause and time scale, and determinism.