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 IdoCohen560/claude-unity-game-studio --skill team-releasegit clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studioWrote 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/idocohen560/claude-unity-game-studio/team-release)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/team-release"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/team-release.svg" alt="Measured on agentmods" 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.00034 | $0.01917 |
| Opus 5 | $0.00017 | $0.00958 |
| Sonnet 5 | $0.00007 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade A, and why
team-release 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 4d 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.
This is a copy
86% identical to team-release — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Argument check: If no version number is provided:
- Read
production/session-state/active.mdand the most recent file inproduction/milestones/(if they exist) to infer the target version. - If a version is found: report "No version argument provided — inferred [version] from milestone data. Proceeding." Then confirm with
AskUserQuestion: "Releasing [version]. Is this correct?" - If no version is discoverable: use
AskUserQuestionto ask "What version number should be released? (e.g., v1.0.0)" and wait for user input before proceeding. Do NOT default to a hardcoded version string.
When this skill is invoked, orchestrate the release team through a structured pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
Team Composition
- release-manager — Release branch, versioning, changelog, deployment
- qa-lead — Test sign-off, regression suite, release quality gate
- devops-engineer — Build pipeline, artifacts, deployment automation
- security-engineer — Pre-release security audit (invoke if game has online/multiplayer features or player data)
- analytics-engineer — Verify telemetry events fire correctly and dashboards are live
- community-manager — Patch notes, launch announcement, player-facing messaging
- producer — Go/no-go decision, stakeholder communication, scheduling
How to Delegate
Use the Task tool to spawn each team member as a subagent:
subagent_type: release-manager— Release branch, versioning, changelog, deploymentsubagent_type: qa-lead— Test sign-off, regression suite, release quality gatesubagent_type: devops-engineer— Build pipeline, artifacts, deployment automationsubagent_type: security-engineer— Security audit for online/multiplayer/data featuressubagent_type: analytics-engineer— Telemetry event verification and dashboard readinesssubagent_type: community-manager— Patch notes and launch communicationsubagent_type: producer— Go/no-go decision, stakeholder communicationsubagent_type: network-programmer— Netcode stability sign-off (invoke if game has multiplayer)
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.
- 4d ago First seen · 149 lines · 34 tokens per session scan A 293fb339117d
team-release is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (18 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,917 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to team-release, differing in 24 lines, and is treated as a copy.
Other skills, from other repositories
archive-issue
Retire a closed issue's working artifacts out of specs/ into the GitHub wiki. Use only when the user asks to archive a finished issue, empty out specs/ for a done task, or move an issue's requirements/architecture/tasks/review/QA docs to the wiki.
start-task
Bootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the…
abd-status
ABD Status agent: read-only dashboard of tasks, findings by severity, blockers, and next actions across all handoff artifacts.
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
standup
Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.
offboard
Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.