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 CodePhobiia/claude-roblox-game-studio --skill estimategit clone --depth 1 https://github.com/CodePhobiia/claude-roblox-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/codephobiia/claude-roblox-game-studio/estimate)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/estimate"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/estimate/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/codephobiia/claude-roblox-game-studio/estimate"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/estimate.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.00028 | $0.00654 |
| Opus 5 | $0.00014 | $0.00327 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
estimate 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 9d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/estimate — Task Estimation
Delegate to: producer (with lead-programmer for tech estimates)
Steps
1. Gather Context
Ask: "What task / feature do you want to estimate?"
2. Break Down Into Sub-Tasks
For a typical feature, list:
- Design: GDD writing (0.5-2 days)
- Implementation: Code writing (1-10 days depending on scope)
- Art assets: If needed (varies wildly)
- Integration: Hooking into existing systems (0.5-2 days)
- Testing: QA plan + execution (0.5-2 days)
- Polish: Rough edges, edge cases (0.5-1 day)
- Review: Code review, design review (0.5 day)
3. Estimate Each Sub-Task
Use T-shirt sizing for unclear items, hours for clear items:
- XS: < 2 hours (trivial)
- S: 2-8 hours (simple)
- M: 1-3 days (moderate)
- L: 3-7 days (complex)
- XL: 1-2 weeks (very complex, consider breaking down)
- XXL: 2+ weeks (must break down further before proceeding)
4. Apply Contingency Buffer
- For tasks with uncertainty: +30-50%
- For tasks in new territory: +50-100%
- For tasks with external dependencies: +variable (explicit risk note)
- For bug fixes: +20% (things hide)
5. Sum and Sanity Check
- Compare to available capacity in current sprint
- Flag if > 40% of sprint capacity (single task dominating the sprint)
- Flag if total breakdown doesn't match vague intuition
6. Present Estimate
# Estimate: [Feature Name]
## Sub-tasks
| Task | Size | Hours (est) | Risk |
|------|------|-------------|------|
| Design GDD | S | 6 | Low |
| Implement core | M | 16 | Medium |
| Implement UI | S | 8 | Low |
| Test + polish | S | 6 | Low |
| Review + iterate | S | 4 | Low |
**Subtotal**: 40 hours
**Contingency** (30%): 12 hours
**Total estimate**: ~52 hours (~6.5 working days)
## Risks
1. [Risk 1 — how it affects estimate]
2. [Risk 2]
## Assumptions
- [Assumption 1]
- [Assumption 2]
## Dependencies
- [Other tasks/systems this depends on]
Output
Present estimate to user. If too large, suggest splitting the feature.
Save estimates to production/sprints/estimates/ when approved.
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.
- 9d ago First seen · 77 lines · 28 tokens per session scan A db6aaaadc714
estimate is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 654 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…