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 skills/code-payments/code-android-app/build-lookupnpx skills add code-payments/code-android-app --skill build-lookupgit clone --depth 1 https://github.com/code-payments/code-android-appWhat 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.00031 | $0.00439 |
| Opus 5 | $0.00015 | $0.00219 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
build-lookup 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 2d 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
Build Lookup: versionCode to commit + CI run
Resolve a Flipcash versionCode to its git commit and the associated GitHub Actions build run.
Background
The Flipcash versionCode is the output of git rev-list --count HEAD at build
time (see apps/flipcash/app/build.gradle.kts:20-25). This means
versionCode N = the Nth commit from the root of the repository.
When someone says "commit 3797" or "build 3797" they mean versionCode 3797.
Usage
Parse $ARGUMENTS for a versionCode (integer). If not provided, ask the user.
Run the helper script:
bash .claude/skills/build-lookup/scripts/build-lookup.sh <versionCode>
The script emits JSON:
{
"version_code": 3797,
"commit": {
"sha": "637722b9c...",
"short": "637722b9c",
"message": "the commit message",
"date": "2026-06-03T..."
},
"total_commits": 3810,
"github_actions": {
"run_id": 26846060877,
"url": "https://github.com/code-payments/code-android-app/actions/runs/26846060877",
"status": "completed",
"conclusion": "success"
}
}
github_actions is null if no matching workflow run was found.
Output
Present the results clearly:
- versionCode: N
- Commit:
<short_sha>—<message>(date) - GitHub Actions: Run #ID — status/conclusion
What ships with it
1 file 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.
- 2d ago First seen · 65 lines · 31 tokens per session scan A e0e357832227
build-lookup is a skill published in the GitHub repository code-payments/code-android-app (23 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 439 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…