Borrowing it
Nothing to install: this file belongs to WesleySalzer/GameCodex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WesleySalzer/GameCodex/main/.claude/commands/publish.mdgit clone --depth 1 https://github.com/WesleySalzer/GameCodexWrote 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/commands/wesleysalzer/gamecodex/publish)<a href="https://agentmods.dev/commands/wesleysalzer/gamecodex/publish"><img src="https://agentmods.dev/badge/commands/wesleysalzer/gamecodex/publish/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/commands/wesleysalzer/gamecodex/publish"><img src="https://agentmods.dev/badge/commands/wesleysalzer/gamecodex/publish.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.00000 | $0.00188 |
| Opus 5.5 | $0.00000 | $0.00075 |
| Sonnet 5.5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
publish 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 1mo 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.
What it actually says
Publish the gamecodex server package to npm.
Steps:
- Verify npm auth:
npm whoami - If not logged in, tell the user to run
! npm loginin the prompt - Build and test:
cd "/Users/s/Documents/Personal/Game Dev/Projects/GameCodex" && npm run build && npm test - Publish:
cd "/Users/s/Documents/Personal/Game Dev/Projects/GameCodex/packages/server" && npm publish --access public - Verify:
npm view gamecodex version(should match packages/server/package.json)
To bump version before publishing:
cd "/Users/s/Documents/Personal/Game Dev/Projects/GameCodex/packages/server" && npm version patch --no-git-tag-version
Token is stored in ~/.npmrc. 2FA is disabled on the account and package. Publishing should work directly without browser auth.
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.
- 1mo ago First seen · 16 lines · 0 tokens per session scan A 5ccd064100d1
publish is a command published in the GitHub repository WesleySalzer/GameCodex (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 188 tokens. 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 commands, from other repositories
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
liveops-brief
Create a concise live operations brief for an event, offer, patch, or campaign.
level-beat
Design or revise level flow, beats, pacing, and encounter structure.
team-live-ops
Orchestrate live-ops team for post-launch content planning.
adopt
Brownfield onboarding audit and migration plan.
explore
Pre-workflow rapid prototyping for exploring multiple game ideas.