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/musingfox/cc-plugins/initnpx skills add musingfox/cc-plugins --skill initgit clone --depth 1 https://github.com/musingfox/cc-pluginsWhat 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.00043 | $0.00752 |
| Opus 5 | $0.00022 | $0.00376 |
| Sonnet 5 | $0.00009 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
init 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
init — Initialize Obsidian Workspace
Run everything directly in the main context — the flow is interactive (AskUserQuestion) by design.
Execution
-
Handle existing config — if
.obsidian.yamlexists in the project root, show a one-line summary (vault name + project) and ask whether to overwrite. -
Pick a vault — list vaults from Obsidian's config and ask the user:
cat ~/Library/Application\ Support/obsidian/obsidian.json \ | jq -r '.vaults | to_entries[] | "\(.key)\t\(.value.path)"'(Linux:
~/.config/obsidian/obsidian.json; Windows:%APPDATA%\obsidian\obsidian.json.) Resolve$VAULT_PATHfrom the chosen entry. -
Ask config options (via
AskUserQuestion):- Project identifier for
/obw:pm? (default = current directory basename; allow "skip" to omit thepmsection) - Default folder for long-form notes? (default
Inbox) - Filename strategy for notes? options:
title/slug/timestamp-title
Mention: daily note folder / filename / template are configured in Obsidian's Daily Notes core plugin, not here. Quick capture always prepends
HH:MMand writes#tagtokens inline (Obsidian indexes them automatically). - Project identifier for
-
Install starter templates — read the Templates folder from
$VAULT_PATH/.obsidian/templates.json:TF=$(jq -r .folder "$VAULT_PATH/.obsidian/templates.json" 2>/dev/null)- If
.obsidian/templates.jsonis missing → tell the user to enable the Templates core plugin in Obsidian, then re-run/obw:init. Stop. - Empty
TFmeans vault root; otherwisemkdir -p "$VAULT_PATH/$TF". - For each of
task.md,doc.md,adr.md:
Never overwrite existing templates. Do not read template contents into the conversation —[ -e "$VAULT_PATH/$TF/task.md" ] || cp "${CLAUDE_PLUGIN_ROOT}/templates/task.md" "$VAULT_PATH/$TF/task.md"cpis enough.
- If
-
Write
.obsidian.yamlusing the template below. Omit thepmsection if skipped.
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 · 70 lines · 43 tokens per session scan A 6d465e3f881d
init is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 752 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-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…