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 icerain-cmd/humanities-superpowers --skill checking-terminology-consistencygit clone --depth 1 https://github.com/icerain-cmd/humanities-superpowersWrote 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/icerain-cmd/humanities-superpowers/checking-terminology-consistency)<a href="https://agentmods.dev/skills/icerain-cmd/humanities-superpowers/checking-terminology-consistency"><img src="https://agentmods.dev/badge/skills/icerain-cmd/humanities-superpowers/checking-terminology-consistency/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/icerain-cmd/humanities-superpowers/checking-terminology-consistency"><img src="https://agentmods.dev/badge/skills/icerain-cmd/humanities-superpowers/checking-terminology-consistency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 103 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00039 | $0.02089 |
| Opus 5 | $0.00019 | $0.01045 |
| Sonnet 5 | $0.00008 | $0.00418 |
| Haiku 4.5 | $0.00004 | $0.00209 |
Grade A, and why
checking-terminology-consistency 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checking Terminology Consistency
Purpose
Control conceptual drift without flattening meaningful variation. This skill distinguishes harmless stylistic variation from changes that alter the argument's object, level of analysis, historical claim, translation, or normative force.
Humanities manuscripts often use several adjacent terms because sources use different vocabularies, translations vary, or a concept develops across sections. Consistency does not mean replacing every word with one preferred label. It means making every variation accountable.
Contract
Accepts a manuscript, chapter set, terminology ledger, concept map, translation notes, style sheet, or reviewer comments about unclear terminology.
Requires the text to be checked and, for central concepts, provisional definitions or evidence of how the researcher intends the terms to differ.
Produces a normalized TerminologyEntry ledger, occurrence map, drift analysis, recommended actions, unresolved researcher decisions, and a terminology gate report.
May produce a translation table, capitalization and hyphenation sheet, abbreviation policy, proper-name authority list, or proposed definition revisions.
Fails when central terms have no recoverable meaning, two terms are used interchangeably despite incompatible definitions, a translation choice cannot be justified, or the requester asks the agent to hide conceptual inconsistency through stylistic editing.
Guarantees that each audited central term is linked to an explicit definition, distinction, status, and recommended treatment.
Does not guarantee that the chosen concept is philosophically correct, that one translation is universally authoritative, or that terminological uniformity will make the argument persuasive.
When to use
Use after the central concepts have been provisionally defined, after merging chapters written at different times, after translation or multilingual research, before manuscript review, after renaming a key concept, or when reviewers report that several terms seem interchangeable.
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 · 261 lines · 39 tokens per session scan A 8b9aa211b016
checking-terminology-consistency is a skill published in the GitHub repository icerain-cmd/humanities-superpowers (16 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 2,089 once invoked, about $0.0002 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-30.
Other skills, from other repositories
batch-translate
Batch process books through the complete pipeline - generate cropped images for split pages, OCR all pages, then translate with context. Use when asked to process, OCR, translate, or batch process one or more books.
qa-eval
Run OCR and translation quality evaluations across scripts and languages. Produces research-grade reports with MCR, cross-model agreement, embedding-space hallucination detection, and corpus readiness scores.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
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.