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/emaballarin/ccplugins/setupnpx skills add emaballarin/ccplugins --skill setupgit clone --depth 1 https://github.com/emaballarin/ccpluginsWhat 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 | $0.00128 | $0.02420 |
| Opus 5 | $0.00064 | $0.01210 |
| Sonnet 5 | $0.00026 | $0.00484 |
| Haiku 4.5 | $0.00013 | $0.00242 |
Grade A, and why
setup 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 yesterday.
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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mf:setup — bootstrap ~/.mindfunnel/
Seed the user's personal ~/.mindfunnel/ directory with the editable scaffolding the other mindfunnel skills depend on. Run once per machine. Idempotent: if ~/.mindfunnel/ already looks complete, say so and stop.
Important
- Never overwrite. Every target file is created only if it doesn't already exist. The user may have already edited
SOUL.mdorUSER.md— destroying them is unacceptable. - Templates live at
${CLAUDE_PLUGIN_ROOT}/templates/. That environment variable is set by Claude Code when this skill runs. Do not hard-code a path; always use the variable. CLAUDE.mdinside~/.mindfunnel/is a symlink toAGENTS.mdin the same directory. This is the standard convention; both names point at the same content.SOUL.mdandUSER.mdare user-global, not project-level. Neither gets stamped into a project root by/mf:prime. This skill symlinks~/.claude/{SOUL,USER}.mdand~/.codex/{SOUL,USER}.mdto the corresponding files in~/.mindfunnel/so both agents reach the same source of truth.
Instructions
Step 1: Ensure ~/.mindfunnel/ exists
mkdir -p "$HOME/.mindfunnel"
Step 2: Seed the four template files (non-destructive)
For each pair below, copy from the bundled template to the target only if the target is absent.
| Template | Target |
|---|---|
${CLAUDE_PLUGIN_ROOT}/templates/AGENTS.md |
~/.mindfunnel/AGENTS.md |
${CLAUDE_PLUGIN_ROOT}/templates/SOUL.md |
~/.mindfunnel/SOUL.md |
${CLAUDE_PLUGIN_ROOT}/templates/USER.md |
~/.mindfunnel/USER.md |
${CLAUDE_PLUGIN_ROOT}/templates/PROJECT.md |
~/.mindfunnel/PROJECT.md.example |
Note the asymmetry: PROJECT.md lands as PROJECT.md.example in ~/.mindfunnel/ because the live PROJECT.md belongs in each project, not in the shared scaffolding. The .example suffix makes that intent obvious.
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.
- yesterday First seen · 189 lines · 128 tokens per session scan A 97aeaf71cbfd
setup is a skill published in the GitHub repository emaballarin/ccplugins (3 stars, last pushed 26d ago), licensed MIT. It adds 128 tokens to every session and 2,420 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…