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 skills add globalize-now/globalize-skills --skill globalize-now-cli-usegit clone --depth 1 https://github.com/globalize-now/globalize-skillsWrote 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/globalize-now/globalize-skills/globalize-now-cli-use)<a href="https://agentmods.dev/skills/globalize-now/globalize-skills/globalize-now-cli-use"><img src="https://agentmods.dev/badge/skills/globalize-now/globalize-skills/globalize-now-cli-use/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/globalize-now/globalize-skills/globalize-now-cli-use"><img src="https://agentmods.dev/badge/skills/globalize-now/globalize-skills/globalize-now-cli-use.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00110 | $0.09155 |
| Opus 5 | $0.00055 | $0.04577 |
| Sonnet 5 | $0.00022 | $0.01831 |
| Haiku 4.5 | $0.00011 | $0.00915 |
Grade A, and why
globalize-now-cli-use 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 9d 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 — 784 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Globalize CLI Usage
This skill guides you through managing translation resources on the Globalize platform using the CLI (globalise-now-cli).
Always use --json when running commands programmatically. Parse JSON output to extract IDs for subsequent commands. Many operations require UUIDs returned from prior steps.
All examples use npx @globalize-now/cli-client. If the CLI is installed globally, replace with globalise-now-cli.
Step 1: Prerequisite Check
Verify authentication is configured:
npx @globalize-now/cli-client auth status --json
If this fails or reports no credentials, run the globalize-now-account-setup skill first.
Step 2: Common Workflow — Create a Project and Connect a Repository
This is the most common end-to-end workflow. Follow these sub-steps in order:
2a. Fetch and match available languages
Projects must be created using language IDs returned from the languages API. Before creating a project, fetch the catalog and match the user's desired languages against it.
- Fetch the language catalog:
npx @globalize-now/cli-client languages list --json
This returns an array of language objects, each with id (UUID), name, and locale (BCP 47 code).
-
Match desired languages against the catalog. Compare the user's source and target locale codes (e.g.,
en,fr,de,ja) against thelocalefield in the returned list. Extract the correspondingidfor each match. -
Report unsupported languages. If any of the user's desired languages do not appear in the catalog, inform the user which languages are unsupported and cannot be added to the project. Do not silently skip them — the user must acknowledge the gap before proceeding. Only continue with languages that have a matching catalog entry.
2b. Create a project
Use the language IDs (UUIDs) matched in step 2a — not bare locale codes:
npx @globalize-now/cli-client projects create \
--name "My App" \
--source-language <SOURCE_LANGUAGE_ID> \
--target-languages <TARGET_LANGUAGE_ID_1> <TARGET_LANGUAGE_ID_2> \
--json
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.
- 9d ago First seen · 784 lines · 110 tokens per session scan A b97a89224bfa
globalize-now-cli-use is a skill published in the GitHub repository globalize-now/globalize-skills (3 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 9,155 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-31.
Other skills, from other repositories
extract-source-sample
Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…
audit-i18n
Audit and fix internationalisation for any web or mobile app. Use when asked to "audit i18n", "fix translations", "add locale", "natural language", "translation quality", "hardcoded strings", "localisation", or "the Japanese feels like Google Translate".
nextjs-locale-monorepo
Add locale-prefixed i18n routing across a Next.js monorepo (Turborepo / pnpm workspaces) by extracting the engine into a shared workspace package that every app consumes — locale detection + a middleware/proxy factory + a use client LocaleProvider/hooks, plus a shared supportedLanguages config. Each app redirects /…
nextjs-locale-standalone
Add locale-prefixed i18n routing to a single (non-monorepo) Next.js App Router site — a middleware/proxy that redirects / and any unprefixed path to / /… using the locale toggle's last choice (the NEXTLOCALE cookie) then the browser's Accept-Language, a [locale] layout with a LocaleProvider + hooks, and a LocaleToggle…
thai-resume
Use this skill for any task involving Thai-language or bilingual (TH/EN) resumes and CVs. Trigger whenever the user asks to: write a Thai resume, draft a CV in Thai, build a bilingual Thai-English resume, format an application for a Thai employer, choose between พ.ศ. and ค.ศ. dates in a CV, or tailor a resume for…
thai-text-processing
Use this skill for any task involving Thai text in code — word segmentation, Unicode normalization, sorting/collation, search indexing, romanization, truncation, or database/Elasticsearch configuration for Thai. Trigger whenever the user asks to: tokenize / segment Thai (no spaces between words), normalize Thai text…