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 wiki-updategit 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/wiki-update)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/wiki-update"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/wiki-update/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/wiki-update"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/wiki-update.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.00068 | $0.01543 |
| Opus 5 | $0.00034 | $0.00772 |
| Sonnet 5 | $0.00014 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
wiki-update 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wiki-update — Targeted Page Edit
Delegate to: wiki-curator (which may delegate to the page's owner)
Arguments
<page>— wiki page path (e.g.,wiki/services/DataStoreService.mdor justDataStoreService)[note]— optional reason or description of the change
When to Use
- User spotted an inaccuracy on a page
- Owner agent wants to refine their page without a new source
- Schema change requires touching multiple pages
- Contradiction resolution
- Adding missing cross-references
- Upgrading a stub to complete status
When NOT to Use
- Ingesting a new raw source → use
/wiki-ingestinstead - Fixing lint issues → use
/wiki-lint --fix - Creating a brand-new page for a topic from scratch with no source → write a proper page via
/wiki-ingestwith a raw source first
Workflow
1. Resolve the Page
If argument is a full path, use it directly. Otherwise, search for the page:
find wiki/ -name "*<arg>*.md" -not -path "wiki/raw/*"
Handle ambiguity: if multiple matches, list them and ask user to disambiguate.
If the page doesn't exist, offer to:
- Create it as a stub (if user wants to start a new page)
- Check if it should be elsewhere (maybe user meant a different category)
2. Read the Page
Load the full page. Note:
owner:,status:,sources:,updated:from frontmatter- Current structure (which sections exist)
- Current
Relatedlinks
3. Read Related Pages
Read every page referenced in the ## Related section. Skim their content to understand the context.
Also load wiki/SCHEMA.md to ensure the edit complies with the schema.
4. Understand the Requested Change
Parse the user's intent:
- Correction — "this is wrong, fix it"
- Expansion — "add info about X"
- Restructure — "split this page" or "merge these sections"
- Cross-reference — "link to Y"
- Status upgrade — "this stub should be complete now"
- Schema conformance — "add missing required sections"
5. Delegate to Owner (If Appropriate)
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 · 192 lines · 68 tokens per session scan A ccc73797ff29
wiki-update is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 1,543 once invoked, about $0.0003 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…