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 emergent-wisdom/sema --skill sema-seedgit clone --depth 1 https://github.com/emergent-wisdom/semaWrote 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/emergent-wisdom/sema/sema-seed)<a href="https://agentmods.dev/skills/emergent-wisdom/sema/sema-seed"><img src="https://agentmods.dev/badge/skills/emergent-wisdom/sema/sema-seed/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/emergent-wisdom/sema/sema-seed"><img src="https://agentmods.dev/badge/skills/emergent-wisdom/sema/sema-seed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.01376 |
| Opus 5 | $0.00039 | $0.00688 |
| Sonnet 5 | $0.00016 | $0.00275 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
sema-seed 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 10d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sema Seed Loop
Generative loop for growing the vocabulary. Pull a random word, think about it openly through the sema lens, mint only if a genuine pattern emerges.
Preflight (once per session)
-
Ask the user about oversight. Default to asking confirmation before each mint:
"Do you want to review each pattern before I mint it, or should I mint autonomously when the four checks pass?"
Set this for the session and stick with it unless told to change mode.
-
Verify minting is enabled.
sema_mintis exposed by default. If it's missing, the deployment has disabled it. Tell the user:"Minting isn't available on this server — it's been disabled via
SEMA_DISABLE_MINT=true. Unset that env var and restart to re-enable." -
Verify the active DB is writable. Call
sema_use()(no args) to see current. If it's the bundled DB, tell the user tosema build my.db --preset fullandsema_use(db_path="my.db")first. -
Offer the UI. Ask: "Want to open the Sema UI to watch new patterns appear?" If yes, invoke the
sema-uiskill.
The run
One word per run, unless the user explicitly asks for more. Most runs end with no mint — that's expected.
Never dismiss a word before reasoning through it. Even words that look obviously trivial, overly abstract, or already covered must go through step 2 first. The reasoning itself is the test — you cannot know whether a word names a missing pattern until you have actually tried to compose existing handles around it. Skipping the thinking and jumping straight to "no, this isn't useful" defeats the purpose of the seed loop.
1. Pull a random word
# macOS has shuf via coreutils; if not, use awk:
awk 'BEGIN{srand()} {print rand() "\t" $0}' /usr/share/dict/words | sort -k1,1 | head -1 | cut -f2-
Or with shuf:
shuf -n 1 /usr/share/dict/words
2. Reason about the word using sema patterns
Output at least 3-4 paragraphs of reasoning where sema handles are woven through the prose as the load-bearing vocabulary. Not a search summary. Not a definition. An actual chain of thought about the word, with handles doing real work in every paragraph.
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.
- 10d ago First seen · 108 lines · 79 tokens per session scan A 3ea63ebcde19
sema-seed is a skill published in the GitHub repository emergent-wisdom/sema (13 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 1,376 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-30.
Other skills, from other repositories
oma-explanation
An offline HTML document that teaches a reader what changed in code, using background information, simple examples, a code walkthrough, and a quiz.
agent-teams
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
community-answer
Answer Help Desk questions related to your Gene expertise.
orchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.
agent-orchestration
Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.