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 agentmods add skills/surfmind-space/awesome-surfmind/term-explainernpx skills add surfmind-space/awesome-surfmind --skill term-explainergit 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/term-explainer)<a href="https://agentmods.dev/skills/surfmind-space/awesome-surfmind/term-explainer"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/term-explainer.svg" alt="Measured on agentmods" 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 | $0.00080 | $0.00506 |
| Opus 5 | $0.00040 | $0.00253 |
| Sonnet 5 | $0.00016 | $0.00101 |
| Haiku 4.5 | $0.00008 | $0.00051 |
Grade A, and why
term-explainer 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 4d 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.
What it actually says
Term Explainer
Scan the page for the technical terms, acronyms, and domain phrases that trip readers up, and define each in plain language with why it matters in this particular context. Never invent a definition, force one meaning onto an ambiguous acronym, or define common words that carry no special domain sense here.
- Extract only the terms that matter for understanding this page: acronyms, specialized phrases, metrics, legal terms, formulas, product names, unfamiliar abbreviations.
- Define each in plain language. Expand acronyms; keep each term's original form and capitalization.
- Tie each definition to how the page uses the term — why it matters here.
- If a term could mean different things in different fields, say so rather than guessing the one the page intends.
- Works in any language: read terms as written, respond in the user's language, and add a transliteration or short gloss for terms in another script.
Report each term with its plain meaning, why it matters here, and any related terms or gotchas. Preserve exact names, numbers, and formatting, and skip words that are merely everyday vocabulary in the page's own language.
Example
Source: a fintech page noting "we report on an EBITDA basis."
EBITDA — Earnings Before Interest, Taxes, Depreciation, and Amortization.
Plain meaning: A measure of profit that strips out interest, taxes, and the accounting charges for aging assets, to approximate the cash earnings from a company's core operations.
Why it matters here: The page is signaling profitability before financing and accounting effects, which usually looks rosier than net income — so it's worth noting what the figure leaves out.
Related terms or gotchas: Not the same as net income or free cash flow; "adjusted EBITDA" can exclude even more and varies by company, so it isn't a standardized figure.
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.
- 4d ago First seen · 35 lines · 80 tokens per session scan A 0d2beae9bac6
term-explainer is a skill published in the GitHub repository surfmind-space/awesome-surfmind (5 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 506 once invoked, about $0.0004 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
cs-master
Expert computer scientist for algorithms, complexity analysis, and distributed systems.
guidance
回答用户关于 QwenPaw 安装与配置的问题：优先定位并阅读本地文档，再提炼答案；若本地信息不足，兜底访问官网文档。.
edu-math-tutorial
数学题分步讲解视频的领域知识。适用场景：(1) 用户给出一道数学题并要求做讲解/ 解题视频；(2) 用户说"讲解这道题"、"生成解题视频"、"make a math tutorial"； (3) 需要中文数学教学视频，涉及方程、公式或几何图形。本 skill 只提供领域 知识（题目拆解、讲解节奏、旁白文案规范、版式与 KaTeX 排版风格）；画面、 配音与成片一律用 Creator 原生 Element 与工具从源头构建。.
video-tutorial-maker
Create scripted tutorial videos with narration, TTS, aligned subtitles, MP4 rendering, and platform variants. Use when Codex needs to create or revise tutorial, explainer, product walkthrough, course, demo, or short-form videos; generate 16:9 landscape output by default unless the user explicitly asks for 9:16, 1:1…
cf-learn
Extract knowledge for human learning from conversation. Auto-invoke on substantial new technical knowledge, debugging breakthroughs, architecture decisions, or complex explanations. Do NOT auto-invoke for trivial edits, typo fixes, or routine operations. Unlike /cf-remember (AI recall), this is educational notes for…
cf-teach
Personal teacher — after a task, explains what happened as a conversational narrative (approach, alternatives, tradeoffs, pitfalls, lessons). Unlike /cf-learn (structured notes), this is a deep-dive so the human understands what happened and why.