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.
git clone --depth 1 https://github.com/emaballarin/ccpluginsWrote 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/plugins/emaballarin/ccplugins/mindfunnel)<a href="https://agentmods.dev/plugins/emaballarin/ccplugins/mindfunnel"><img src="https://agentmods.dev/badge/plugins/emaballarin/ccplugins/mindfunnel/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/plugins/emaballarin/ccplugins/mindfunnel"><img src="https://agentmods.dev/badge/plugins/emaballarin/ccplugins/mindfunnel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mf 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 6d 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.
What it actually says
{
"name": "mf",
"version": "0.8.0",
"description": "mindfunnel — project-agnostic Claude Code session management. Seven slash-command skills: /mf:setup seeds ~/.mindfunnel/ (AGENTS, SOUL, USER, PROJECT templates) and the ~/.claude/ + ~/.codex/ symlinks to the user-global baseline and personal files; /mf:prime stamps a committed project-scoped AGENTS.md + intra-repo CLAUDE.md symlink + empty PROJECT.md in the current project; /mf:dump consolidates session state into Claude Code's auto-memory dir; /mf:spinup reads it back at the start of the next session; /mf:park saves the session scratchpads into the project before a reboot (triaged, every copy verified) and /mf:unpark restores them afterwards; /mf:author is the reference for writing the documents an agent reads — skills, AGENTS.md, CLAUDE.md — covering context pointers, the context-load / cognitive-load pair, progressive disclosure, completion criteria, leading words and pruning.",
"author": {
"name": "Emanuele Ballarin"
},
"homepage": "https://github.com/emaballarin/ccplugins/tree/main/plugins/mindfunnel",
"repository": "https://github.com/emaballarin/ccplugins",
"license": "MIT",
"keywords": [
"memory",
"session",
"workflow",
"mindfunnel",
"auto-memory",
"scaffolding",
"ledger",
"provenance",
"skill-authoring",
"prompt-engineering"
]
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 716 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago Changed 298cc2e8694d
- 12d ago Changed 32594cdad197
- 13d ago Changed 5df0d0649bdc
- 19d ago Changed 4ec49d1e86f6
- 22d ago Changed 1c57c1ebb996
- 1mo ago Changed 44184e81d4df
- 1mo ago First seen · 24 lines scan A 28052b22b6e3
mf is a plugin published in the GitHub repository emaballarin/ccplugins (4 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
operations
Program management, process design, vendor and supplier management, and operational delivery.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
people
Org design, hiring and interviewing, compensation and leveling, and workforce planning.
open-source
Collection of skills for open-source R and Python package developers.
cross-code-organizer
Inspect and organize Claude Code memories, skills, MCP servers, hooks, and project context from a local dashboard.
han-linear
Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.