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 ekline-io/ekline-docs-skills --skill terminologygit clone --depth 1 https://github.com/ekline-io/ekline-docs-skillsWrote 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/ekline-io/ekline-docs-skills/terminology)<a href="https://agentmods.dev/skills/ekline-io/ekline-docs-skills/terminology"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/terminology/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/ekline-io/ekline-docs-skills/terminology"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/terminology.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.00055 | $0.00825 |
| Opus 5 | $0.00028 | $0.00413 |
| Sonnet 5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
terminology 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 11d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Terminology
Check documentation for terminology consistency against approved terms.
Reference: references/terminology-rules.md contains all approved terms, variants to avoid, and formatting rules.
Terminology Checking Process
Step 1: Load Approved Terms
Read references/terminology-rules.md to get:
- Product and feature names (exact capitalization)
- Technical terms (programming, infrastructure)
- Action verbs (preferred vs avoided)
- UI element terms
- Prohibited terms
Step 2: Extract Terms from Document
Identify all potentially controlled terms:
- Product/feature names
- Technical concepts
- UI element names
- Code identifiers mentioned in prose
- Action verbs in instructions
Step 3: Compare Against Approved List
For each term found:
├── Is it in the approved list?
│ YES → Check for exact match (case, spacing)
│ NO → Flag for review
│
└── Does it match a "variant to avoid"?
YES → Flag as terminology violation
NO → Continue
Step 4: Check Consistency Within Document
Even if a term isn't in the controlled list:
- Is it used consistently throughout?
- First usage should establish the pattern
- All subsequent uses should match
Step 5: Return Findings
Internally, create a terminology report with the following structure.
terminology_report:
document: "path/to/file.md"
violations:
- term_found: "api-key"
approved_term: "API key"
rule_reference: "references/terminology-rules.md#technical-terms"
locations: ["line 42", "line 87"]
severity: error
inconsistencies:
- term: "config file"
variants_found: ["config file", "configuration file"]
locations:
"config file": ["line 10"]
"configuration file": ["line 45"]
recommendation: "Use 'configuration file' consistently"
severity: warning
undefined_terms:
- term: "webhook"
first_use: "line 23"
recommendation: "Add definition or link to glossary"
severity: info
summary:
errors: 2
warnings: 1
info: 1
compliant: false
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 122 lines · 55 tokens per session scan A 185a5ead6954
terminology is a skill published in the GitHub repository ekline-io/ekline-docs-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 825 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…