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 DojoGenesis/mcp --skill seed-curatorgit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/seed-curator)<a href="https://agentmods.dev/skills/dojogenesis/mcp/seed-curator"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/seed-curator.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.1 | $0.00031 | $0.00756 |
| Opus 5 | $0.00015 | $0.00378 |
| Sonnet 5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
seed-curator 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 7d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seed Curator
Manages the full seed lifecycle — from planting raw patterns through harvesting session insights to elevating proven seeds into reusable skills.
Workflow
1. MODE
Determine the operation from user intent:
- plant — Extract a new seed from a specific experience or insight
- harvest — Scan a recent session for candidate seeds
- search — Find seeds relevant to a current situation
- elevate — Promote a proven seed to a full SKILL.md
- audit — Check seed library health
2. PLANT (when mode = plant)
Extract a reusable pattern:
- Name: Short, memorable, hyphenated (e.g.,
compilation-as-contract) - Source: Where this pattern was observed (session, project, incident)
- Confidence: 0.0-1.0 based on how many times it's been validated
- Tags: 3-5 categorization tags
- Pattern: What the seed captures — the reusable insight
- When to use: Situations where this seed applies
- Example: Concrete instance of the pattern in action
- Counter-example: When this pattern does NOT apply Write as YAML-fronted markdown file.
3. HARVEST (when mode = harvest)
Scan the current or recent session for seed candidates:
- Corrections received from the user (feedback → pattern)
- Approaches that worked unexpectedly well (success → pattern)
- Non-obvious decisions that required investigation (discovery → pattern)
- Friction points that were resolved (obstacle → pattern) Present candidates to user for confirmation before writing files.
4. SEARCH (when mode = search)
Given a situation description, score all seeds by relevance:
- Tag match (exact tag = 3 points, partial = 1)
- Description keyword overlap (each matching word = 1 point)
- Confidence weighting (score × confidence) Return ranked list with seed name, confidence, and one-line relevance explanation.
5. ELEVATE (when mode = elevate)
For seeds meeting promotion criteria:
- Confidence ≥ 0.8
- Applied 3+ times across different contexts
- No contradicting seeds in the library Generate a SKILL.md draft following the skill-creation skill's format:
- YAML frontmatter with name, description, triggers, version
- Structured workflow steps derived from the seed's pattern
- Anti-patterns derived from the seed's counter-examples
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.
- 7d ago First seen · 81 lines · 31 tokens per session scan A 6aefa9349662
seed-curator is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 756 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.
Other skills, from other repositories
memory-index
Index a folder's contents into the MemPalace semantic memory for search and retrieval. Use this skill whenever the user asks to "index a folder", "index a directory", "index memory", "mine a project into memory", "make a folder searchable", "embed a folder", "ingest code into the palace", or "index this directory for…
memory-mine
Mine project files or conversations into the MemPalace memory system. Indexes source code and conversation history as searchable palace drawers with semantic embeddings and room assignment.
memory-status
Show MemPalace memory system status — drawer counts, wings, rooms, knowledge graph stats, and embedding model state.
notebrain-assistant
Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like…
cartographer-ops
Configure, operate, troubleshoot, or upgrade a Cartographer server or client; connect agents and manage Knowledge Bases.
fkf-learn
Stage verified fkf findings as reviewable wiki or project diffs. Use after a durable decision, pattern, status change, dead end, or skill lesson.