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 process-extractiongit 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/process-extraction)<a href="https://agentmods.dev/skills/dojogenesis/mcp/process-extraction"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/process-extraction/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/dojogenesis/mcp/process-extraction"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/process-extraction.svg" alt="Reviewed on agentmods" width="80" 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.00069 | $0.02136 |
| Opus 5.5 | $0.00028 | $0.00854 |
| Sonnet 5.5 | $0.00014 | $0.00427 |
| Haiku 4.5 | $0.00007 | $0.00214 |
Grade A, and why
process-extraction 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 1mo 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Extraction
I. Philosophy: From One-Off Process to Institutional Knowledge
Every time someone completes a complex task successfully, they generate implicit knowledge -- a sequence of decisions, actions, and course corrections that led to a good outcome. This implicit knowledge is valuable, but it's also fragile: it lives in a single conversation, a single mind, a single moment. Without capture, it evaporates.
Process extraction is the discipline of making implicit knowledge explicit. The key insight is that you must document the specific process before abstracting the general pattern. The specific is the anchor. Without it, generalization drifts into theory.
The process example is the proof. The skill is the tool. You cannot build a reliable tool without first understanding -- in concrete detail -- what the tool must do.
II. When to Use This Skill
- After completing a complex, multi-step task that produced a good outcome and is likely to be repeated
- When you find yourself repeating the same sequence of actions across different projects or contexts
- During a retrospective when a successful workflow is identified for standardization
- When onboarding someone to a complex process that needs to be reproducible
- When a conversation transcript contains a valuable workflow that should be preserved
- When institutional knowledge exists only in one person's head and needs to be formalized
- After a debugging session that revealed a systematic diagnostic approach
When NOT to use: If the process was unsuccessful, capture it as a retrospective lesson, not a skill. If the process is trivial (1-2 steps), it doesn't warrant a skill.
III. The Extraction Workflow
Step 1: Document the Specific Process
Goal: Create a detailed record of what actually happened, not what should have happened.
Actions:
- Identify the source: conversation transcript, memory, or user description
- Create a process example document with these sections:
- Context: When and why the process was used
- Input: What the process started with
- Output: What the process produced
- Steps Taken: Every significant action, in order, with goals and outcomes
- Key Decisions: What was decided, why, and what alternatives were considered
- What Worked: Success factors and why they mattered
- What Was Hard: Challenges encountered and how they were resolved
- Reusable Pattern: The generalizable principle (the kernel of the future skill)
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.
- 1mo ago First seen · 196 lines · 69 tokens per session scan A 4d11553e4836
process-extraction is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 2,136 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
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.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
lsp-implement
Find all concrete implementations of an interface or abstract type. Use when you need to know what types satisfy an interface, or what subtypes exist before changing a base type.
lsp-local-symbols
Fast file-scoped symbol analysis — find all usages of a symbol within the current file, list all symbols defined in the file, and get type info at a position. Use when you need local-scope analysis without a workspace-wide search.
Linux Malware Analysis
Expert ELF malware analysis — packing, toolchain ID, kill chain, persistence, C2, rootkits, cryptominers, Go/Rust/Mirai patterns, MITRE ATT&CK mapping.