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 hoatv2211/GameStudio-CodexKIT --skill mmorpg-packet-protocol-reviewgit clone --depth 1 https://github.com/hoatv2211/GameStudio-CodexKITWrote 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/hoatv2211/gamestudio-codexkit/mmorpg-packet-protocol-review)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/mmorpg-packet-protocol-review"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/mmorpg-packet-protocol-review/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/hoatv2211/gamestudio-codexkit/mmorpg-packet-protocol-review"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/mmorpg-packet-protocol-review.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.00044 | $0.00723 |
| Opus 5 | $0.00022 | $0.00362 |
| Sonnet 5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
mmorpg-packet-protocol-review 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MMORPG Packet Protocol Review
Overview
Compare versioned protocol manifests across clients and servers without sending traffic or editing generated packet definitions.
When to use
Use for opcode drift, packet-version mismatch, direction errors, typed field order changes, request-response mismatches, or mixed client/server releases.
When NOT to use
Do not use for exploit testing, live packet replay, generic Lua copy auditing, or runtime service control.
Required inputs and context discovery
Collect protocol versions, source and generated paths, packet names, opcodes, direction, authority, ordered typed fields, response pairing, build compatibility matrix, and no-touch generated outputs.
Safety and risk level
Read-only. Never send crafted packets, start servers, capture credentials, or hand-edit generated protocol outputs.
Workflow
- Identify authoritative protocol sources and version ownership. Completion criterion: every manifest is source, generated, copy, or unknown.
- Normalize packet definitions into deterministic ordered structures. Completion criterion: parse ambiguity is reported rather than guessed.
- Compare versions, presence, opcode, direction, authority, fields, and pairing. Completion criterion: each mismatch cites both sides.
- Map mismatches to supported client/server build combinations. Completion criterion: compatibility risk is explicit.
- Propose source-first changes and regression fixtures. Completion criterion: no live traffic or generated hand edit is required.
Evidence and output contract
Produce packet-protocol-review.json with versions, compatibility, packet mismatches, source authority, limitations, and recommended source fixes.
Handoff contract
Record manifest/build paths, supported versions, mismatches, generated files, parsing limits, and next source-first owner.
Pitfalls and anti-rationalization
- Matching packet names do not prove compatibility.
- Field order is part of a binary contract.
- Do not test static drift by sending packets to production.
- Generated copies are not automatically authoritative.
What ships with it
3 files 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 First seen · 79 lines · 44 tokens per session scan A 43c2bbb042b4
mmorpg-packet-protocol-review is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 723 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
code-standards
C# coding standards and code review. Use when the user mentions coding standards or conventions, writing code to spec, defining standards for a project, cohesion and coupling, design pattern selection, or naming conventions, or wants a code review on the design and standards dimension.
codex-sdd:validate
Check implementation alignment with specification, detect drift between planned design and actual code. Fourth phase of OpenSpec workflow.
vibe-spec-sync
Bidirectional sync between specification documents and code. Detects spec drift from staged changes, updates spec to reflect approved decisions, and ensures every commit represents a reconciled snapshot of spec, tests, and code.
vibe-gap-analysis
Assesses production readiness or audits a codebase against its specs. Supports quick static mode, deep 17-dimension audit, or single-dimension focus.
vibe-devil-advocate-review
Challenges recommendations, designs, or synthesis by adversarial review across 5 dimensions. Use before shipping any significant recommendation or design document.
vibe-iteration-review
Performs end-of-iteration review with quality grading, metrics, and trend analysis. Use at the end of each development iteration or sprint.