verify

A verification guide for building, starting, and using a repository's console app in a real browser. It covers the local server entry point, ports, rebuilds, and stale build files.

In plain words
What is it for?
Running end-to-end checks after code changes, confirming the correct server and port, and restarting the app after rebuilding.
Why use it?
It reduces the risk of declaring a change working when the built app does not start or the browser is connected to another agent session.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ninemindai/agentgem/verify
Any agent
npx skills add ninemindai/agentgem --skill verify
Clone the repo
git clone --depth 1 https://github.com/ninemindai/agentgem

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 648 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00648
Opus 5 $0.00013 $0.00324
Sonnet 5 $0.00005 $0.00130
Haiku 4.5 $0.00003 $0.00065

Measured 3d ago against content hash e292d8ebc37c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

verify scanned grade C with 2 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 3d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- **After pulling a refactor, clean `dist/` first** — `rm -rf dist tsconfig.tsbuildinfo

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- SSE surfaces are also curl-able directly, e.g.
.claude/skills/verify/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verifying agentgem changes at the running surface

Build + launch

pnpm build                       # tsc -b AND the console SPA bundle — both required
AGENTGEM_HOME=$(mktemp -d) PORT=<unused-port> node dist/client.js
  • Entry is dist/client.js (the local-mode server) — NOT dist/index.js, which no longer exists after the server-library extraction into @agentgem/app. The banner is agentgem (client mode) listening at ….
  • After pulling a refactor, clean dist/ firstrm -rf dist tsconfig.tsbuildinfo packages/*/tsconfig.tsbuildinfo && pnpm build. Stale incremental output can leave a dead dist/index.js importing a since-removed package (e.g. @agentgem/deploy), which crashes on boot.
  • Always restart the server after a rebuild — it caches the console SPA HTML at boot, and built-in miniapp constants (e.g. EMBER_HTML) are module-level imports.
  • Pick a genuinely unused port and confirm ownership: with concurrent agent sessions in sibling worktrees, another session's server may already hold your port and your node exits after printing its banner. Check lsof -p $(lsof -tnP -iTCP:<port> -sTCP:LISTEN) | grep cwd points at YOUR worktree.
  • AGENTGEM_HOME isolates agentgem's own data; watched transcripts still come from the real ~/.claude, so Watch/hygiene/Ember surfaces show real sessions.

Drive

  • Console pages are hash routes: http://localhost:<port>/#/arcade, #/watch, #/play, …
  • Browser consent for Play capabilities is per-origin localStorage (agentgem:play:consent:<gem>:<cap>) — a reused port silently skips consent modals; clear those keys to test the consent path.
  • Sealed miniapp iframes are null-origin: you cannot reach inside from the top document. To observe the broker wire, wrap window.EventSource in the top window (streams live there), or listen for message events (game→host half is visible on window).
  • SSE surfaces are also curl-able directly, e.g. curl -N "http://localhost:<port>/api/watch/hygiene?file=<transcript>".

Read the full file on GitHub · 48 lines

Changes

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.

  1. 3d ago First seen · 48 lines · 25 tokens per session scan C e292d8ebc37c

Subscribe to this mod's changes

verify is a skill published in the GitHub repository ninemindai/agentgem (39 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 648 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.