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/goshippo/ai/address-validationnpx skills add goshippo/ai --skill address-validationgit clone --depth 1 https://github.com/goshippo/aiWrote 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/goshippo/ai/address-validation)<a href="https://agentmods.dev/skills/goshippo/ai/address-validation"><img src="https://agentmods.dev/badge/skills/goshippo/ai/address-validation.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.00017 | $0.00973 |
| Opus 5 | $0.00009 | $0.00487 |
| Sonnet 5 | $0.00003 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
address-validation 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address Validation
Address Field Format
The Shippo API uses v1 field names for address components in most endpoints (including CreateShipment). Always use:
| Field | Description | Example |
|---|---|---|
name |
Full name | Jane Smith |
street1 |
Street address line 1 | 731 Market St |
street2 |
Street address line 2 (optional) | Suite 200 |
city |
City | San Francisco |
state |
State or province | CA |
zip |
Postal code | 94103 |
country |
ISO 3166-1 alpha-2 country code | US |
email |
Email (required for international senders) | [email protected] |
phone |
Phone (required for international senders) | +1-555-123-4567 |
Note: CreateAddress and ValidateAddress take the v2 field names (address_line_1, city_locality, state_province, postal_code), but when passing addresses inline to CreateShipment, you must use the v1 names above.
Validate a Structured Address
- Collect at minimum:
street1,city,state,zip,country(ISO 3166-1 alpha-2). - Call
CreateAddresswith the address fields. This creates the address and returns an object ID. - Call
ValidateAddresswith the address fields to get validation results. Note: this endpoint takes address fields as query parameters, not an object ID. - Check
analysis.validation_result.valuein the response. Values:"valid","invalid", or"partially_valid"(address found with corrections applied). Checkanalysis.validation_result.reasonsfor details. - Report the standardized address back. Highlight any corrected fields (listed in
changed_attributes). Noteanalysis.address_type("residential","commercial", or"unknown") -- residential classification affects carrier surcharges. - If invalid: relay the reason descriptions. If the API returns a
recommended_address, present it to the user. - If
partially_valid: show what was corrected and ask the user to confirm the corrections are acceptable.
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.
- 4d ago First seen · 88 lines · 17 tokens per session scan A d0c6f5e5a0cf
address-validation is a skill published in the GitHub repository goshippo/ai (2 stars, last pushed 22d ago), licensed MIT. It adds 17 tokens to every session and 973 once invoked, about $0.0001 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
shop
Use when the user wants Axon-backed product research, product comparisons, review synthesis, budget-aware recommendations, or cart preparation without checkout.
cmdb-patterns
Create ServiceNow CIs and cmdbrelci relationships, walk upstream/downstream impact, detect orphan/stale CIs, and align discovered CIs with the proper sysclassname hierarchy.
blast-radius
Trace ServiceNow configuration dependencies — what artifacts touch a given field, what calls a script include, table/app-level config inventory. Use before deletes, renames, or refactors.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
mobile-development
Configure ServiceNow Mobile (Now Mobile/Agent) — syssgmobileapp screens, card builders, push notifications, offline sync rules, mobile actions for barcode/GPS, and offline-queue change processing.