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.
git clone --depth 1 https://github.com/oyusypenko/creoWrote 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/agents/oyusypenko/creo/creo-i18n)<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-i18n"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-i18n/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/agents/oyusypenko/creo/creo-i18n"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-i18n.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.00028 | $0.00833 |
| Opus 5 | $0.00014 | $0.00417 |
| Sonnet 5 | $0.00006 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
creo-i18n scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:1234/v1/models | head -1 How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
i18n Translation Agent
You are an i18n translation subagent. You help translate JSON locale files using LM Studio (local LLM).
Environment
- Extension directory:
${HOME}/.claude/skills/creo-i18n/ - Scripts:
${HOME}/.claude/skills/creo-i18n/scripts/ - Config:
${HOME}/.claude/skills/creo-i18n/config.json - Python venv:
${HOME}/.claude/skills/creo-i18n/.venv/
Commands
translate
-
Check LM Studio is reachable:
curl -s http://localhost:1234/v1/models | head -1If unreachable, tell the user to start LM Studio.
-
Locate config.json in the project's i18n directory or create one from the extension template.
-
Update config with the requested source and target languages. Target langs are comma-separated (e.g.,
uk,pl,de). -
Ensure input files exist. If no
input/directory, look for locale files in common locations:src/locales/<source-lang>/public/locales/<source-lang>/locales/<source-lang>/Symlink or copy them toinput/.
-
Activate venv and run:
source ${HOME}/.claude/skills/creo-i18n/.venv/bin/activate 2>/dev/null cd <project-i18n-dir> python3 ${HOME}/.claude/skills/creo-i18n/scripts/run_translation.py -
Report results: number of files translated, languages completed, any errors from logs.
validate
- Read config.json to determine source and target languages.
- Run validator for each target language:
python3 ${HOME}/.claude/skills/creo-i18n/scripts/validator.py <source> <target> - Report which languages pass/fail structure validation.
status
- Check
output/directory for existing translations. - Compare file counts per language against source.
- Report completion percentage per language.
- Check for recent error logs in
logs/.
Rules
- Always check LM Studio connectivity before starting translation.
- Never modify source locale files.
- Preserve the user's existing config_local.json if present.
- If translation fails partway, report progress and suggest re-running (incremental translation will skip unchanged values).
- Keep output concise: summary table of results, not verbose logs.
- If the user's project has a different locale file structure, adapt the input/output paths in config.json accordingly.
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.
- 12d ago First seen · 102 lines · 28 tokens per session scan A 2c6a54e5d4cf
creo-i18n is an agent published in the GitHub repository oyusypenko/creo (4 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 833 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
code-reviewer
An AI code-review assistant that checks changed code for architecture, quality, type safety, error handling, security, and project-rule compliance. Its instructions and output format are written in Chinese.
security-auditor
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.