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-mintgit 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-mint)<a href="https://agentmods.dev/skills/emergent-wisdom/sema/sema-mint"><img src="https://agentmods.dev/badge/skills/emergent-wisdom/sema/sema-mint.svg" alt="Measured on agentmods" 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.00043 | $0.02747 |
| Opus 5 | $0.00022 | $0.01373 |
| Sonnet 5 | $0.00009 | $0.00549 |
| Haiku 4.5 | $0.00004 | $0.00275 |
Grade A, and why
sema-mint 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 8d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minting Sema Patterns
Minting creates a new content-addressed pattern in the sema vocabulary. The definition IS the identity — hash the content, get the name. Change one invariant, get a different hash.
Before you start a minting session
1. Check that minting is enabled. sema_mint is exposed by default. If it's missing from your available MCP tools, the server has been explicitly configured to hide it. Tell the user:
"Minting isn't available on this server — it's disabled via
SEMA_DISABLE_MINT=true. Unset that env var and restart to re-enable."
2. Make sure the active DB is writable. The bundled vocabulary is read-only — minting into it will be blocked with an error. If the user wants to mint, they need a project DB:
sema build my-project.db --preset full
sema use my-project.db
Or use sema_use(db_path="...") via MCP.
3. Offer the UI. Ask: "Want to open the Sema UI to watch the patterns appear as they get minted?" If yes, invoke the sema-ui skill. The UI refreshes every 5 seconds locally, so each new pattern appears within a few seconds of being minted.
When to mint
Minting is rare. Before minting, search at least three different glosses. Only mint when:
- You've explained the same concept 3+ times across conversations
- The concept has stable, non-negotiable invariants
- Another agent needs the exact protocol to coordinate
- A graph concept has been refined 3+ times (stable enough to crystallize)
The pipeline
sema_mint(pattern_json) runs a full validation + hash + store pipeline:
- Parse — JSON syntax check
- Schema validate — required fields, handle format, taxonomy path validity
- Dependency wiring — every
{{placeholder}}in text must be declared in dependencies; every declared dependency must be used - DAG check — no cycles in the dependency graph; topological sort
- Layer direction — lower layers cannot depend on higher layers (Infrastructure < Physics < Mind < Society)
- Merkle hash — hash only the semantic fields to produce the content-addressed identity
- Store — add to vocabulary database with computed
sema_id,sema_ref,sema_stub
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.
- 8d ago First seen · 251 lines · 43 tokens per session scan A 7f8975808ec8
sema-mint is a skill published in the GitHub repository emergent-wisdom/sema (13 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 2,747 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-30.
Other skills, from other repositories
agent-teams
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
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.
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.
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.
Agent Orchestrator
Coordinate multiple AI agents and skills for complex workflows.
Agentic Orchestration for Oracle
Multi-agent coordination patterns for enterprise AI systems on Oracle Cloud Infrastructure.