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 hoatv2211/GameStudio-CodexKIT --skill studio-workspace-routinggit clone --depth 1 https://github.com/hoatv2211/GameStudio-CodexKITWrote 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/hoatv2211/gamestudio-codexkit/studio-workspace-routing)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/studio-workspace-routing"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/studio-workspace-routing/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/hoatv2211/gamestudio-codexkit/studio-workspace-routing"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/studio-workspace-routing.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.00038 | $0.00832 |
| Opus 5 | $0.00019 | $0.00416 |
| Sonnet 5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
studio-workspace-routing 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 today.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Studio Workspace Routing
Overview
Route work through one project-profile seam so repository ownership, project-local facts, and verification stay local while reusable workflow logic stays in the kit.
When to use
Use when .agents/project-profile.yaml exists, the workspace contains nested Git roots, ownership is unclear across client/server/services, or one feature crosses repositories.
When NOT to use
Do not use for a single known repository and subsystem with an already selected owner skill. Do not replace project intake when the profile is missing or unverified.
Required inputs and context discovery
Collect the workspace root, profile path, current repository snapshots, requested goal, candidate paths, cross-project contract, exclusions, owner skills, and declared validation commands.
Safety and risk level
This skill is read-only. It selects scope and evidence; it does not authorize edits, builds, services, database operations, publishing, or agent activation.
Workflow
- Load and validate the project profile before routing. Completion criterion: invalid, missing, or stale ownership remains Unverified or BLOCKED. Overlapping declared capability patterns remain valid profile metadata; exact concurrent assignment conflicts are checked after agent templates and inferred roles resolve.
- Select one repository and subsystem owner for repository-local work. Completion criterion: one owner skill, write scope, and do-not-touch scope are explicit.
- Split cross-project contracts into ordered repository phases. Completion criterion: authority, interface handoffs, and integration ownership are named.
- Choose the narrowest declared validation for each phase. Completion criterion: every phase has a command, risk level, expected artifact, or explicit BLOCKED state.
- Hand the bounded route to the owning workflow and re-route if scope changes. Completion criterion: sibling repositories are not changed for convenience.
Evidence and output contract
Produce workspace-route.json with profile snapshot, selected repository, subsystem, owner skill, phase, owned paths, exclusions, validation, authority, and evidence labels.
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.
- today Changed · +1 lines 77c9a427e3b1
- 8d ago First seen · 80 lines · 38 tokens per session scan A b001bfe24d54
studio-workspace-routing is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 832 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-31.
Other skills, from other repositories
vibe-cherry-pick-integration
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
vibe-rollback-plan
Documents rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment.
vibe-pre-commit-audit
Scans staged changes for secrets, debug statements, TODOs without references, and other common commit mistakes. Use before creating any commit.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.