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 surfmind-space/awesome-surfmind --skill terminology-keepergit clone --depth 1 https://github.com/surfmind-space/awesome-surfmindWrote 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/surfmind-space/awesome-surfmind/terminology-keeper)<a href="https://agentmods.dev/skills/surfmind-space/awesome-surfmind/terminology-keeper"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/terminology-keeper/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/surfmind-space/awesome-surfmind/terminology-keeper"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/terminology-keeper.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.00069 | $0.00581 |
| Opus 5 | $0.00034 | $0.00291 |
| Sonnet 5 | $0.00014 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
terminology-keeper 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 10d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminology Keeper
Keep translations consistent across a page, document, product copy, legal text, docs, or domain material by building a glossary of the recurring domain terms and applying the same preferred translation throughout.
How To Work
- Extract recurring domain terms, acronyms, product names, and terms of art from the source.
- Build a glossary table:
Source term | Preferred translation | Context | Notes. - Apply the glossary consistently in the translated or rewritten output.
- When a term has competing translations in the source, pick one preferred form, normalize every occurrence to it, and note the alternates.
- Flag terms that need user or domain-expert confirmation.
Output Format
Use concise headings. Include these sections when they fit:
- Glossary
- Translated or revised text
- Terms needing confirmation
Guardrails
- Preserve important names, numbers, links, code, formatting, dates, currencies, and user constraints.
- Do not over-translate brand or code terms; keep do-not-translate items verbatim.
- When a term has multiple valid translations across subdomains (legal vs. medical vs. financial), choose by the document's domain and record the assumption rather than picking casually.
- If the source is inconsistent and you cannot tell which translation is correct, surface it under terms needing confirmation instead of guessing.
Respond in the same language as the user's request unless the skill explicitly involves translation or localization.
Example
Source (EN → ES) mixes translations of the same term: "The Plaintiff filed the claim. Later, the claimant amended the same claim, and the demandante withdrew it."
Glossary
Source term Preferred translation Context Notes claim demanda legal filing not reclamación in this context Plaintiff / claimant demandante the party suing normalize both source variants to one term Translated text (es): "El demandante presentó la demanda. Más tarde, el demandante modificó la misma demanda y la retiró."
Terms needing confirmation: Source used "Plaintiff" and "claimant" interchangeably — confirm both refer to the same party before finalizing.
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.
- 10d ago First seen · 55 lines · 69 tokens per session scan A 4fa3f70ff8dc
terminology-keeper is a skill published in the GitHub repository surfmind-space/awesome-surfmind (5 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 581 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-08-31.
Other skills, from other repositories
iflytek-text-proofread
A tool that checks Chinese writing through iFlytek’s official document-proofreading service. It looks for spelling, punctuation, wording, factual, terminology, and sensitive-content problems.
iflytek-translate
A text-translation tool that uses iFlytek's machine-translation service and supports more than 70 language pairs. It can translate text supplied directly, through standard input, or from a file.
iflytek-video-translate
A tool that translates a video’s speech into another language and creates dubbed audio. Video localization means adapting video content for viewers who speak a different language.
yida-i18n
A tool for managing the languages and translated text in YiDA applications, including which languages are enabled and the wording shown on pages.
aso-marketing
Optimize App Store and Google Play listings via a 7-phase, plan-approval-gated ASO workflow (keyword strategy, metadata, localization). Don't use for web SEO, paid UA campaigns, or pre-submission compliance audits.
azure-translator
Expert knowledge for Azure Translator development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using translate/detect/dictionary APIs, Custom Translator, glossaries, document jobs, or Docker containers…