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 mattmre/EVOKORE-MCP-PUBLIC --skill cross-project-process-minergit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/cross-project-process-miner)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/cross-project-process-miner"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/cross-project-process-miner/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/mattmre/evokore-mcp-public/cross-project-process-miner"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/cross-project-process-miner.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.00049 | $0.03438 |
| Opus 5 | $0.00024 | $0.01719 |
| Sonnet 5 | $0.00010 | $0.00688 |
| Haiku 4.5 | $0.00005 | $0.00344 |
Grade A, and why
cross-project-process-miner 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Project Process Miner
Purpose
The broadest view in the retrospective system: aggregates session data from every project slug in ~/.claude/projects/ and surfaces findings that appear in 3+ different projects. These are systemic process issues, not project-specific quirks, and they feed directly into global CLAUDE.md updates rather than per-repo fixes.
Where session-retrospective-miner answers "what happened in this project's recent sessions," this skill answers "which process problems show up everywhere, regardless of project type."
All Project Slugs ──► Cross-Project Process Miner ──► Systemic Findings
(~/.claude/ │
projects/) ▼
Patterns appearing in 3+ projects
│
▼
Global CLAUDE.md + skill updates
When To Use This Skill
Trigger it when:
- You suspect an efficiency problem is systemic rather than project-specific
- Planning a global CLAUDE.md refresh
- Before authoring a new top-level skill or guardrail
- After multiple per-project retrospectives surface the same kind of finding
- Quarterly process review across your full workspace
Prerequisites
This skill uses two MCP tools from EVOKORE-MCP plus direct JSONL parsing:
session_analyze_replay— tool usage + retry signals across session replay logssession_work_ratio— per-session work density
Both tools are available in EVOKORE v3.1+. Verify with discover_tools before running.
Input Parameters
min_projects_for_pattern: 3 # minimum distinct projects a pattern must appear in
time_window: "last-30-days" # or "last-7-days" | "this-week" | "all-time"
focus: "all" # or "tool-efficiency" | "narrative-quality" | "agent-spawns"
output_format: "report" # or "claude-md-patch"
min_session_turns: 10 # skip trivial/exploratory sessions
project_exclude: [] # optional list of project slugs to exclude
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 · 340 lines · 49 tokens per session scan A fb85251a9c32
cross-project-process-miner is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 3,438 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-09-03.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
stakeholder-alignment
Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).
wrongstack-kanban
Record substantial project work on WrongStack's IPC-backed Kanban board so it survives the session and other agents can see it. Covers card detail, the managed Backlog→Todo→Running→Review→Done lifecycle, lease-fenced dispatch, and what "verified" means before a card reaches Done.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
shared-monorepo-nx
Nx monorepo build system — workspace configuration, project graph, task pipelines, caching, generators, plugins, and release management.