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-usagegit 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-usage)<a href="https://agentmods.dev/skills/emergent-wisdom/sema/sema-usage"><img src="https://agentmods.dev/badge/skills/emergent-wisdom/sema/sema-usage/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-usage"><img src="https://agentmods.dev/badge/skills/emergent-wisdom/sema/sema-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 48 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00068 | $0.03386 |
| Opus 5.5 | $0.00027 | $0.01354 |
| Sonnet 5.5 | $0.00014 | $0.00677 |
| Haiku 4.5 | $0.00007 | $0.00339 |
Grade A, and why
sema-usage 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 21d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Speak in Sema
Sema is a content-addressed vocabulary protocol. Several hundred patterns that give you precise, shared words for concepts that would otherwise require paragraphs of re-explanation. Each pattern has a handle (e.g. StateLock#c9c2) that is a cryptographic commitment to its definition — two agents using the same handle are provably talking about the same thing.
Before defining a concept from scratch, check if sema already has a word:
sema_searchwith the ideasema_resolveto read mechanism and invariants- Use the handle as a load-bearing noun in your text: "This uses
StateLock#c9c2to prevent concurrent mutation"
Not footnotes — actual words you think with.
When the user wants to see patterns visually
If the user asks to "see", "view", "show", or "explore" patterns visually — or asks to see the graph or browse the vocabulary — invoke the sema-ui skill to launch http://localhost:3030. The local view gives them a pattern browser, search, and a 3D graph that grows as you mint. When you start building a vocabulary with the user, offer it once so they can watch the work.
Session memory
The server tracks which patterns you've already seen. Subsequent searches return compact results for known patterns (handle + gloss + _seen: true). Just use the handle — the full definition is already in your context. Call sema_resolve only if you need to re-read a pattern's mechanism.
Call sema_reset_session() if your context was compressed or you need full results again.
The workflow
- Search —
sema_search({ query: "trust model" })— find existing patterns by meaning - Resolve —
sema_resolve({ handle: "TrustModel#7859" })— read full definition, mechanism, invariants - Handshake —
sema_handshake({ ref: "X#1234" })— verify exact meaning before relying on a handle - Mint —
sema_mint({ pattern_json: "..." })— create a new pattern (rare!)
Switching and managing databases
The CLI and MCP server are separate processes with separate DB state. sema use on the CLI does NOT affect the running MCP server. Always use the MCP tool for switching:
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.
- 21d ago Changed · +2 lines 23abc5a98096
- 22d ago Changed · +2 lines · +29 tokens per session 5230753c2791
- 1mo ago Changed 8472fdfa0aec
- 1mo ago Changed · +12 lines 0696375552e7
- 2mo ago First seen · 237 lines · 39 tokens per session scan A 95975566c5fe
sema-usage is a skill published in the GitHub repository emergent-wisdom/sema (14 stars, last pushed 19d ago), licensed MIT. It adds 68 tokens to every session and 3,386 once invoked, about $0.0003 per session on Opus 5.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
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
hive-mind-advanced
Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory.
hive-mind-advanced
Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory.
cross-agent-handoff
Transfer context between AI agent sessions with structured handoff protocols, state serialization, and decision log preservation. Covers multi-agent coordination, context compression, and continuity patterns. Triggers on agent handoff, session transfer, or multi-agent continuity requests.
compact-s
A context-saving procedure that writes important conversation state to a checkpoint file before context is shortened. Context shortening removes older conversation detail to make room for more work.
hive-mind-advanced
Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory.