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 agentmods add commands/sbenson2/gamelens/publishgit clone --depth 1 https://github.com/sbenson2/GameLensWrote 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/sbenson2/gamelens/publish)<a href="https://agentmods.dev/commands/sbenson2/gamelens/publish"><img src="https://agentmods.dev/badge/commands/sbenson2/gamelens/publish.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00161 |
| Opus 5 | $0.00000 | $0.00081 |
| Sonnet 5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
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 4d 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 gamelens 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 ~/Developer/GameCodex && npm run build && npm test - Publish:
cd ~/Developer/GameCodex/packages/server && npm publish --access public - Verify:
npm view gamelens version(should match packages/server/package.json)
To bump version before publishing:
cd ~/Developer/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.
- 4d ago First seen · 16 lines · 0 tokens per session scan A d13cc4fe7afd
publish is a command published in the GitHub repository sbenson2/GameLens (1 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 161 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
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
Prepare a release by updating docs and bumping the version.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.