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/hellothisworld/agent-skill-verification-template/glossarynpx skills add HelloThisWorld/agent-skill-verification-template --skill glossarygit clone --depth 1 https://github.com/HelloThisWorld/agent-skill-verification-templateWrote 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/hellothisworld/agent-skill-verification-template/glossary)<a href="https://agentmods.dev/skills/hellothisworld/agent-skill-verification-template/glossary"><img src="https://agentmods.dev/badge/skills/hellothisworld/agent-skill-verification-template/glossary.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.00051 | $0.00820 |
| Opus 5 | $0.00026 | $0.00410 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
glossary 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Glossary (Wikipedia)
A Claude-style skill that answers glossary <term> requests by looking the
term up on English Wikipedia and returning a definition rendered as a web
page, where every factual claim is backed by a file:line citation into the
fetched article. It is built to be verified like a production component — see
skill-contract.json for the machine-readable contract
and verification-rules.md for how outputs are graded.
When to use
Use this skill for requests such as glossary Mexico or glossary Switzerland.
The term after glossary is looked up; the skill produces a concise,
source-grounded definition and a self-contained HTML page for it.
Tools
| Tool | Purpose |
|---|---|
wikipedia_search |
Search the offline Wikipedia snapshot cache. Returns {title, file, line, text} matches, best article first. |
wikipedia_fetch |
Read a snapshot and return its structured article data plus the citable "lede" line. |
Contract rule: wikipedia_search must be used before wikipedia_fetch.
Offline-first design
Like the rest of this template, the default eval runs fully offline and
deterministically. npm run glossary:build-cache fetches each term once from
English Wikipedia (MediaWiki action API) and writes a citable snapshot to
fixtures/wikipedia/<term>.html. Each snapshot embeds a machine-readable
glossary-data JSON block and a lede line that contains the exact query
term verbatim, so citations stay valid even when Wikipedia's canonical title
or opening phrasing differs from the query. After the cache exists, no network
is required to run or verify the skill.
Procedure
- Parse the term from the
glossary <term>request. - Use
wikipedia_searchto locate the best-matching snapshot. - Use
wikipedia_fetchto read the snapshot and confirm the citable line. - Produce a structured answer whose claim cites that
file:line. - If no snapshot matches the term, return
insufficient_evidencewith an emptyclaimsarray. Never invent a definition or a citation.
What ships with it
3 files 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.
- 3d ago First seen · 76 lines · 51 tokens per session scan A dbfeed6152cd
glossary is a skill published in the GitHub repository HelloThisWorld/agent-skill-verification-template (1 stars, last pushed 11d ago), licensed MIT. It adds 51 tokens to every session and 820 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
know-code-teach
Explain architecture, decisions, and trade-offs to the human BEFORE making code edits and while coding. Use at session start, before any non-trivial implementation or refactor, when the user asks what is being built or why, after a know-code gate deny (before the quiz), or when the human is unfamiliar with the area.…
create-interactive-slides
발표문·강의안·제품 시연을 스토리보드로 구조화하고 체험형 또는 시연형 HTML·CSS·JavaScript 슬라이드로 제작·검증한다. 내용에 맞는 인터랙션, 발표자 노트, 시연 cue, 리허설과 fallback이 필요할 때 사용한다. 일반 PPTX 편집이나 정적인 문서 작성에는 사용하지 않는다.
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.