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 TabooHarmony/roblox-brain --skill roblox-publish-checklistgit clone --depth 1 https://github.com/TabooHarmony/roblox-brainWrote 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/tabooharmony/roblox-brain/roblox-publish-checklist)<a href="https://agentmods.dev/skills/tabooharmony/roblox-brain/roblox-publish-checklist"><img src="https://agentmods.dev/badge/skills/tabooharmony/roblox-brain/roblox-publish-checklist/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/tabooharmony/roblox-brain/roblox-publish-checklist"><img src="https://agentmods.dev/badge/skills/tabooharmony/roblox-brain/roblox-publish-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00027 | $0.00673 |
| Opus 5.5 | $0.00011 | $0.00269 |
| Sonnet 5.5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
roblox-publish-checklist 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 12d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roblox Publish Checklist
When to Load
Load before publishing or updating a live experience. Test the surfaces and risks the change introduces.
Quick Reference
1. Define the release
Record the changed places, scripts, assets, configuration, schemas, products, supported devices, and rollback path. Classify each gate as required, conditional, or not applicable before testing.
2. Block on high-consequence failures
- Persistence changed: load, save, migration, duplicate-session, disconnect, and shutdown behavior. Load
roblox-dataorroblox-server-data. - Remotes or authority changed: validate types, bounds, state, ownership, replay, and abusive frequency. Load
roblox-networkingandroblox-security. - Purchases changed: test durable, idempotent receipt grants and retries. Load
roblox-monetization. - Cloud auth or webhooks changed: verify secrets, scopes, callback state, retries, signatures, and deduplication. Load
roblox-cloud.
A failed high-consequence gate means NOT READY. Do not average it into a percentage. Precedence: user approval authorizes an otherwise permitted action; it does not satisfy a mandatory policy and does not turn a failed or unverified gate into PASS.
3. Exercise the shipped surface
- Run one normal flow plus failure, retry, leave/rejoin, and rapid-input cases relevant to the change.
- Test every supported input mode and representative viewport/device tier.
- Measure errors, memory, frame/network cost and streaming.
- Verify focus, touch targets, readable contrast, non-color state cues, reduced motion, and localized overflow where applicable.
- Confirm Dashboard metadata, permissions and policy; after publishing, verify the version actually serving players.
4. Require evidence
Every PASS cites a test, log, profiler capture, readback, screenshot, or dashboard inspection. UNVERIFIED if unavailable; approval is not evidence.
Output
READY, NOT READY, or READY WITH ACCEPTED RISK; blockers first, then warnings, unverified gates, evidence, rollback plan, and skipped gates with reasons.
What ships with it
1 file 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.
- 12d ago Changed · +3 lines 37eac43452a4
- 1mo ago Changed 262b018388ea
- 1mo ago First seen · 50 lines · 27 tokens per session scan A 573510203a98
roblox-publish-checklist is a skill published in the GitHub repository TabooHarmony/roblox-brain (134 stars, last pushed 13d ago), licensed MIT. It adds 27 tokens to every session and 673 once invoked, about $0.0001 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
releasing-godot-prompter
Use when cutting a GodotPrompter release or bumping its version — the version-bump sequence, tag-triggered workflow, and the marketplace manifests that must follow.
changelog-generator
Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.
release-manager
Automates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates.
release-orchestrator
Orchestrate end-to-end release pipelines. Use when running pre-release validation, generating changelogs, bumping semantic versions, scoring deployment readiness, or gating releases with secret scanning and GO/NO-GO checks.
gm-finalize
Seal the current tag: snapshot the per-tag working docs into docs/tags/ /, write a CHANGELOG entry, run git tag, and reset per-tag runtime state for the next /gm-gdd round. Does NOT package a release — that lives in a separate skill. Explicit invocation only — use /gm-finalize.
roblox-release-operations
Run Roblox release operations. Use for pre-publish checklists, smoke tests, release notes, staged rollout thinking, rollback plans, live issue response, release gates, version readiness, and post-release monitoring.