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 tech-debtgit 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/tech-debt)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/tech-debt"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/tech-debt/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/tech-debt"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/tech-debt.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.00030 | $0.00752 |
| Opus 5 | $0.00015 | $0.00376 |
| Sonnet 5 | $0.00006 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
tech-debt 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tech-debt — Technical Debt Catalog
Delegate to: lead-programmer (with technical-director for architecture debt)
Steps
1. Search for Debt Markers
grep -rn "TODO\|FIXME\|HACK\|XXX\|DEPRECATED" src/ --include="*.lua" --include="*.luau"
2. Search for Known Anti-Patterns
# Deprecated APIs
grep -rn "[^.]wait(" src/ | grep -v "task.wait\|:Wait"
# Magic numbers in gameplay
grep -rn "[^a-zA-Z_][0-9]\{3,\}" src/ServerScriptService src/ServerStorage
# Stringy bools
grep -rn "== \"true\"\|== \"false\"" src/
3. Catalog Each Item
For each piece of debt:
- Location: file:line
- Category: Architecture / Code Quality / Performance / Security / Documentation
- Description: What's wrong
- Severity: Critical / High / Medium / Low
- Estimated fix cost: hours or T-shirt size
- Impact if ignored: What breaks or gets worse
- Suggested fix approach: High-level plan
4. Score and Prioritize
Priority = Impact / Cost
High-impact, low-cost items go first.
5. Categorize
Architecture Debt
- Coupling problems
- Missing abstractions
- Circular dependencies
- Inconsistent patterns
Code Quality Debt
- Duplicated code
- Magic numbers
- Missing type annotations
- Commented-out code
Performance Debt
- Inefficient algorithms
- Missing caching
- Unoptimized hot paths
- Memory leaks
Security Debt
- Missing validation
- Client-trust assumptions
- Deprecated security APIs
- Missing rate limits
Documentation Debt
- Missing GDD sections
- Out-of-date comments
- No architecture diagrams
- Missing ADRs
6. Generate Report
# Tech Debt Inventory
**Date**: YYYY-MM-DD
**Total items**: X
**Estimated total cost**: Y hours
## By Category
- Architecture: X items
- Code Quality: X items
- Performance: X items
- Security: X items
- Documentation: X items
## Top 10 Priority Items
| # | Location | Issue | Category | Severity | Cost | Priority Score |
|---|----------|-------|----------|----------|------|----------------|
| 1 | src/combat/hit.lua:42 | No input validation | Security | High | 1h | 9/10 |
| 2 | ... | ... | ... | ... | ... | ... |
## Critical Items (fix ASAP)
1. [Description]
## Quick Wins (high impact, low cost)
1. [Description]
## Long-term Investments
1. [Description — worth doing but not urgent]
## Recommendations
- Allocate ~15% of each sprint to debt paydown
- Fix critical items this sprint
- Schedule quick wins for next sprint
- Plan dedicated refactor sprint for architecture items
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.
- 8d ago First seen · 117 lines · 30 tokens per session scan A 9ba209eaa73f
tech-debt is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 752 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-09-03.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…