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 agentmods add skills/dojogenesis/mcp/seed-librarynpx skills add DojoGenesis/mcp --skill seed-librarygit 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-library)<a href="https://agentmods.dev/skills/dojogenesis/mcp/seed-library"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/seed-library.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.00083 | $0.03149 |
| Opus 5 | $0.00042 | $0.01574 |
| Sonnet 5 | $0.00017 | $0.00630 |
| Haiku 4.5 | $0.00008 | $0.00315 |
Grade A, and why
seed-library 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 5d 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seed Library
Version: 1.1 Author: Tres Pies Design Purpose: Manage and apply the 10 Dojo Seed Patches plus 3 field seeds as reusable thinking modules.
I. Philosophy: Seeds as Thinking Modules
The 10 Dojo Seed Patches are not abstract theory -- they are battle-tested patterns that emerged from real enterprise agent research. Each seed encodes a specific principle that, when applied at the right moment, prevents costly mistakes and accelerates delivery.
Seeds are thinking modules, not checklists. They change how you approach a problem, not just what you do. The meta-seed -- "Governance Multiplies Velocity" -- captures this essence: structure doesn't slow you down, it speeds you up by eliminating rework, ambiguity, and wasted exploration.
The library exists to make these patterns accessible. When you face a complex problem, the right seed should surface within seconds, not require 30 minutes of digging through documentation.
II. When to Use This Skill
- Architecting a new system or feature and need proven patterns
- Keywords match seed triggers: governance, multi-agent, context, token, cost, routing, trace, safety, infrastructure, complexity
- Someone asks "What seed applies here?" or "Which pattern should I use?"
- Debugging unexpected behavior and need a framework for investigation
- Optimizing costs or performance and need a structured approach
- Designing multi-agent coordination and need routing patterns
When NOT to use: For seeds that emerged from your own experience (not the Dojo Seed Patches), use the seed-extraction skill. This library is specifically the curated collection of 10 enterprise-grade patterns.
III. The 10 Dojo Seed Patches
1. Three-Tiered Governance
Pattern: Strategic / Tactical / Operational layers provide clear decision frameworks at every level.
Trigger keywords: governance, capabilities, complexity, coordination, policy, standards
What it refuses: Flat governance where everything is decided at one level.
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.
- 5d ago First seen · 382 lines · 83 tokens per session scan A f4b05d9ae175
seed-library is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 3,149 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
prune-npm-overrides
Audit the pnpm overrides a repo already carries, remove the ones upstream has since fixed, and require a justification comment on every one that stays. The counterpart to fix-npm-vulnerability. Use when asked to check, clean up, or prune the overrides, or when an override's tracking issue comes up for review.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
engflow-artifacts
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.