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 protomated/protomated-plugins-official --skill spanish-intakegit clone --depth 1 https://github.com/protomated/protomated-plugins-officialWrote 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/protomated/protomated-plugins-official/spanish-intake)<a href="https://agentmods.dev/skills/protomated/protomated-plugins-official/spanish-intake"><img src="https://agentmods.dev/badge/skills/protomated/protomated-plugins-official/spanish-intake/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/protomated/protomated-plugins-official/spanish-intake"><img src="https://agentmods.dev/badge/skills/protomated/protomated-plugins-official/spanish-intake.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.00088 | $0.01642 |
| Opus 5.5 | $0.00035 | $0.00657 |
| Sonnet 5.5 | $0.00018 | $0.00328 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
spanish-intake 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spanish-intake — Spanish-Language Intake & Client Communication
⚠️ AI-ASSISTED DRAFT — ATTORNEY REVIEW REQUIRED This is a translation-assist tool, not a certified translation or interpretation. Where a certified interpreter is legally required (e.g., in-court proceedings, sworn statements, certain government filings), this skill does not substitute for one. Every fact and every translated phrase must be reviewed before this is relied on, filed, or sent. Not legal advice.
This skill works in two directions, and asks which one applies if it isn't obvious from what's provided:
- Spanish → English (intake): turns Spanish-language intake notes or a voicemail transcript into a structured English intake summary for the file.
- English → Spanish (client communication): turns an English draft communication (a letter, status update, or intake acknowledgment) into a natural Spanish version for the client.
This skill only works from what you provide. It never invents a fact that isn't in the source notes, and it never silently resolves an ambiguous or idiomatic phrase by guessing — it flags the phrase and asks, in both directions.
Invocation
/spanish-intake
/spanish-intake [paste Spanish-language intake notes or voicemail transcript]
/spanish-intake [paste English draft to translate to Spanish]
If neither the direction nor the source text is clear, ask before proceeding:
"Are we turning Spanish intake notes into an English summary, or an English draft into Spanish? Paste or attach the source text and I'll go from there."
Workflow
Direction A — Spanish intake notes → English structured summary
Step 1 — Collect the source. Read from pasted text or an attached file (intake notes, a voicemail transcript, a completed Spanish-language intake form). If the source is a transcript with unclear or garbled sections (common with voicemail transcription), note those sections explicitly rather than guessing at what was said.
Step 2 — Extract and structure the information, translating into English as you go. Mark any field as [Not provided] if the source doesn't cover it — do not infer or fabricate:
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.
- 1mo ago First seen · 135 lines · 88 tokens per session scan A 057f2ac47e46
spanish-intake is a skill published in the GitHub repository protomated/protomated-plugins-official (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,642 once invoked, about $0.0004 per session on Opus 5.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-04.
Other skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
docs-governance
Use when writing, restructuring, auditing, or reviewing Cherry Studio repository documentation, READMEs, JSDoc, comments, Agent instructions, or paired English/Chinese docs, including source-linked documentation impact checks.