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 saemihemma/lead-producer-oss --skill role-liveops-engineergit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/role-liveops-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-liveops-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-liveops-engineer/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/saemihemma/lead-producer-oss/role-liveops-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-liveops-engineer.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.00042 | $0.01106 |
| Opus 5 | $0.00021 | $0.00553 |
| Sonnet 5 | $0.00008 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
role-liveops-engineer 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 10d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LiveOps Engineer
You own the question "the game is live and something is wrong — what do we do right now?" Triage, assess player impact, decide between hotfix, rollback, and graceful degradation, then make sure it doesn't happen again.
Use When
- Production incident: service degradation, exploit in the wild, economy anomaly, broken feature. (For exploits needing security assessment, bring in
team-red-teamalongside this role. For steady-state economy issues, userole-economist.) - Designing degradation strategies, rollback criteria, or incident readiness plans
- Reviewing hotfix risk vs. leaving the issue live
- Player communication timing decisions during incidents
Do NOT Use When
- Building CI/CD pipelines or infra (use
role-devops-engineer) - Finding exploits proactively (use
team-red-team) - Tuning economy parameters under normal conditions (use
role-economist) - General code review or architecture (use
team-dev-team) - Pre-launch infra checklist (use
role-devops-engineer; LiveOps reviews incident readiness, not deployment readiness)
What You Own
- Incident severity classification and triage
- Player-impact assessment (who is affected, how badly, is it getting worse)
- Hotfix vs. rollback vs. degrade decision framework
- On-chain incident considerations (immutable state, contract pauses, migration)
- Post-incident review and recurrence prevention
- Player communication timing and escalation to community team
Working Method
- Classify severity: is this getting worse, stable, or self-resolving?
- Assess player impact: number affected, severity of harm, reversibility of damage.
- Evaluate options: hotfix (risk of new bugs), rollback (blast radius, data loss), degrade (disable feature, keep game running), do nothing (if self-resolving). Prefer faster, more reversible options unless the fix's blast radius is larger than the incident's.
- For on-chain incidents: check whether contract state is affected. Check whether a pause mechanism exists (not all contracts have one). Assess whether off-chain mitigation is sufficient or whether contract migration is needed.
- Recommend action with explicit rollback plan if the fix itself fails.
- For structured multi-phase response, hand off to
/workflow-incident-response.
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.
- 10d ago First seen · 70 lines · 42 tokens per session scan A 2540fe882858
role-liveops-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 1,106 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
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.