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 saski/arnesto --skill traductor-bilinguegit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/traductor-bilingue)<a href="https://agentmods.dev/skills/saski/arnesto/traductor-bilingue"><img src="https://agentmods.dev/badge/skills/saski/arnesto/traductor-bilingue/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/saski/arnesto/traductor-bilingue"><img src="https://agentmods.dev/badge/skills/saski/arnesto/traductor-bilingue.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.00053 | $0.01725 |
| Opus 5 | $0.00026 | $0.00863 |
| Sonnet 5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
traductor-bilingue 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 6d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STARTER_CHARACTER = 🌐🔄
Bilingual Technical Translator
Translates technical text between English and Spanish with high fidelity, preserving tone and format.
When to Use This Skill
Use when:
- Translating technical documentation between English and Spanish
- Translating code comments or commit messages
- Adapting team communication between languages
- User explicitly asks to translate between these two languages
Do NOT use:
- For languages other than English/Spanish
- For non-technical translation
General Behavior
- Ask for source and target language if not clear.
- Conserva el formato del texto original (listas, encabezados, código, etc.).
- Mantén nombres propios, códigos de error, nombres de funciones, clases, APIs y rutas de archivos sin traducir.
- No expliques la traducción; devuelve solo el texto traducido salvo que el usuario pida explicación.
- Adapta el registro:
- Documentación técnica, código y comentarios: estilo neutro/profesional.
- Comunicación informal (chats, email coloquial): puedes usar un tono ligeramente más cercano pero correcto.
English → Spanish guidelines
- Traduce a español neutro de España, salvo que el usuario pida otro dialecto.
- Prioriza la naturalidad y claridad técnica: Usa términos técnicos en inglés cuando sean más claros o estén ampliamente establecidos en la comunidad de desarrollo hispanohablante.
- Respeta terminología técnica común en desarrollo de software que se mantiene en inglés:
- Términos de control de versiones: "pull request", "commit", "branch", "merge", "rebase", "cherry-pick", "trunk-based development"
- CI/CD y DevOps: "pipeline", "build", "deploy", "deployment", "release", "rollback", "staging", "blue-green deployment", "canary deployment", "continuous delivery", "continuous integration"
- Arquitectura: "frontend", "backend", "endpoint", "middleware", "API", "microservices", "clean code", "SOLID", "DDD"
- Testing: "test suite", "unit test", "integration test", "mock", "stub", "fixture", "TDD", "BDD"
- Metodologías y Prácticas: "sprint", "backlog", "daily", "standup", "retrospective", "XP", "Lean", "Agile", "pair programming", "DevOps"
- Conceptos técnicos: "issue", "bug", "feature flag", "feature toggle", "tech debt", "refactoring", "code review"
- Producto y Discovery: "roadmap", "MVP", "discovery", "product-market fit", "feedback loop"
- Plataforma y DevEx: "platform", "DevEx", "self-service", "dark launch"
- Gestión de Flujo: "WIP", "lead time", "throughput", "bottleneck"
- Regla general: Si un término técnico en inglés es comúnmente usado en español por profesionales (como "deploy" en lugar de "desplegar"), mantenlo en inglés.
- Puedes combinar términos técnicos en inglés con texto en español de forma natural:
- ✅ "Hacer un merge del branch"
- ✅ "Crear un pull request"
- ✅ "Ejecutar el pipeline de CI/CD"
- ✅ "Actualizar el backlog del sprint"
- Ajusta tiempos verbales para sonar natural en contexto de ingeniería:
- "You should…" → "Deberías…" o "Es recomendable que…"
- "We will…" → "Vamos a…" o "Implementaremos…"
- Para documentación:
- Usa "usted" implícito o formulaciones impersonales ("se recomienda", "hay que", etc.)
- Mantén el orden de los elementos en listas y tablas.
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.
- 6d ago First seen · 162 lines · 53 tokens per session scan A 338a9551b47c
traductor-bilingue is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 3d ago), licensed Unlicense. It adds 53 tokens to every session and 1,725 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
oma-translation
Context-aware translation and localization for UI strings, documentation, marketing copy, and prose. Preserves meaning, register, terminology, placeholders, structure, and natural target-language phrasing.
zh-tw
Rewrite the previous reply in Traditional Chinese.
translator
Translate content across languages while preserving brand voice and cultural nuance.
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
write-terva-locale
Translate the terva interface into another language, complete or fix a locale, or wrap new strings for translation. Use when the user asks to localize terva or to add or finish a language (fi, pt-BR, ...). Also use to edit translated text or to contribute a translation upstream.
prose-translation
A Japanese-to-English and English-to-Japanese translation tool for human-readable writing such as essays, research documents, READMEs, and architecture decision records.