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/nyaruka/phonenumbers/sync-upstreamnpx skills add nyaruka/phonenumbers --skill sync-upstreamgit clone --depth 1 https://github.com/nyaruka/phonenumbersWrote 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/nyaruka/phonenumbers/sync-upstream)<a href="https://agentmods.dev/skills/nyaruka/phonenumbers/sync-upstream"><img src="https://agentmods.dev/badge/skills/nyaruka/phonenumbers/sync-upstream.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.00124 | $0.02894 |
| Opus 5 | $0.00062 | $0.01447 |
| Sonnet 5 | $0.00025 | $0.00579 |
| Haiku 4.5 | $0.00012 | $0.00289 |
Grade A, and why
sync-upstream 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync with upstream libphonenumber
This package is a Go port of google/libphonenumber, tracking its Java reference implementation. A sync is two independent operations — do them in order, but understand they're different in kind:
- Metadata regen — mechanical. Rebuild the embedded
data/blobs from a new upstream release. Fully automated bycmd/buildmetadata. - Code reconciliation — judgment. Port new Java logic changes into the Go files. Can't be automated; this is the real reason SYNC.md exists.
State lives in SYNC.md: the code baseline (Code reconciled against vX.Y.Z)
and the deliberate divergences (what we intentionally do not port). Read it first. The
embedded-metadata version is tracked separately in the generated metadata/version.go
(metadata.Version) — never hand-edit that.
Run everything from the repo root (/Users/rowan/nyaruka/phonenumbers).
Argument
The skill takes one optional argument selecting which operation(s) to run:
/sync-upstream data— Phase 1 only (metadata regen). An automated metadata update can invoke this mode directly./sync-upstream code— Phase 2 only (code reconciliation, against the metadata version already built — see the note at the top of Phase 2)./sync-upstream— both phases, in order.
Whichever mode runs, finish with Finalize below: commit the changes and stop. This skill
never releases — no tag, no push, no CHANGELOG.md. The user cuts releases separately
with /release.
Phase 1 — Metadata regen (mechanical)
go run ./cmd/buildmetadata # latest upstream release
# go run ./cmd/buildmetadata v9.0.32 # or pin a specific tag
This resolves the target tag, wipes and re-clones upstream into _build/ (a shallow
--depth=1 checkout at the target tag — gitignored), rebuilds every embedded blob
(data/, metadata/data/, carrier/data/, geocoding/data/, timezone/data/), and
rewrites the generated metadata/version.go with the tag it built from.
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 · 214 lines · 124 tokens per session scan A b2193c689ddf
sync-upstream is a skill published in the GitHub repository nyaruka/phonenumbers (1,600 stars, last pushed 3d ago), licensed MIT. It adds 124 tokens to every session and 2,894 once invoked, about $0.0006 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
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
markdown
Markdown formatting rules for this project. Apply when writing or editing any .md or .mdx file, including documentation and website content.
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
gmeasure
Benchmark and measure Go code with gmeasure — an Experiment groups named Measurements, recorded via RecordValue/RecordDuration/MeasureDuration or repeated Sample/SampleValue/SampleDuration with SamplingConfig, timed inline with a Stopwatch, summarized through GetStats/Stats (StatMin/Max/Mean/Median/StdDev…
video-production
Produce programmable videos with Remotion using scene planning, asset orchestration, and validation gates for automated, brand-consistent video content.