launch-store: Skill for Claude Code

.claude/skills/add-a-glossary-topic/SKILL.md

add-a-glossary-topic is a skill for Claude Code from YosefHayim/launch-store. It costs 45 tokens per session (251 once invoked), scanned A, original, MIT.

A skill for adding a teaching entry to launch-store's shared glossary, the source used to explain project terms and steps.

In plain words
What is it for?
Use it when adding a new concept, command step, or store term. It also covers updating the related tests and running the project checks.
Why use it?
It keeps explanations in one place so both glossary commands and step explanations use the same text instead of drifting apart.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is YosefHayim/launch-store's own configuration. It tells Claude Code how to work on launch-store itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything launch-store configures →

Reuse

Borrowing it

Nothing to install: this file belongs to YosefHayim/launch-store. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/YosefHayim/launch-store/main/.claude/skills/add-a-glossary-topic/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/YosefHayim/launch-store

Made for: Claude Code.

Wrote 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.

agentmods badge for add-a-glossary-topic

README.md
[![agentmods](https://agentmods.dev/badge/skills/yosefhayim/launch-store/add-a-glossary-topic/github.svg)](https://agentmods.dev/skills/yosefhayim/launch-store/add-a-glossary-topic)
Your own site
<a href="https://agentmods.dev/skills/yosefhayim/launch-store/add-a-glossary-topic"><img src="https://agentmods.dev/badge/skills/yosefhayim/launch-store/add-a-glossary-topic/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.

agentmods 80×15 button for add-a-glossary-topic

Your own site · 80×15
<a href="https://agentmods.dev/skills/yosefhayim/launch-store/add-a-glossary-topic"><img src="https://agentmods.dev/badge/skills/yosefhayim/launch-store/add-a-glossary-topic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 251 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00251
Opus 5 $0.00023 $0.00125
Sonnet 5 $0.00009 $0.00050
Haiku 4.5 $0.00005 $0.00025

Measured 12d ago against content hash 0b49f8180bf2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

add-a-glossary-topic 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 12d 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.

.claude/skills/add-a-glossary-topic/SKILL.md · 22 lines

What it actually says

Add a glossary topic

Use this when

  • adding a launch explain topic
  • adding teaching text for a new concept, step, or store term

Steps

  1. Add the topic to src/core/terminal/glossary.ts - the single source for teaching text. It feeds both launch explain and the --explain step expansions; never duplicate the strings elsewhere.
  2. Bump the topic count in src/core/terminal/glossary.test.ts (expect(topics.length).toBe(N)) by the number of topics you added, and add a toContain(...) assertion per new topic.
  3. Run the gate.

The toBe(N) count is a known merge hotspot: if a concurrent PR also added a topic, the count collides. On rebase, sum both additions rather than taking one side, and keep both topics.

See AGENTS.md.

Changes

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.

  1. 12d ago First seen · 22 lines · 45 tokens per session scan A 0b49f8180bf2

Subscribe to this mod's changes

add-a-glossary-topic is a skill published in the GitHub repository YosefHayim/launch-store (8 stars, last pushed 15d ago), licensed MIT. It adds 45 tokens to every session and 251 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-31.