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/jotnpx skills add musingfox/cc-plugins --skill jotgit 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.00084 | $0.00848 |
| Opus 5 | $0.00042 | $0.00424 |
| Sonnet 5 | $0.00017 | $0.00170 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
jot 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jot — Capture or Note
Single triage skill. Decide the mode, then run the obsidian CLI directly — no sub-agent. Before any CLI call, invoke the obsidian:obsidian-cli skill to load exact syntax — never run obsidian help/--help to discover it. If .obsidian.yaml is missing, tell the user to run /obw:init and stop.
Mode selection
Inspect the user's input:
- cap mode — short text (one line / a sentence),
#tagtokens, no explicit title, journaling/log verbs. Goes to today's daily note. - note mode — explicit title, multi-line body, "create a note on X", document-shaped content. Goes to a vault folder (per
.obsidian.yamlnoteconfig). - ambiguous — call
AskUserQuestionwith two options: "Quick capture (daily note)" and "New long-form note".
cap mode
Append a timestamped bullet to today's daily note. Nothing more. Daily note folder / filename / template are owned by Obsidian's Daily Notes core plugin.
- If body is empty, prompt for content.
- Compose bullet:
- HH:MM — <body>(any#tagtokens stay inline — Obsidian indexes them automatically). - Append the bullet to today's daily note via
daily:append(creates the note if missing). - Confirm with the appended line. Return
[[<daily-note-basename>]].
Example: 記一下 #worklog 完成了 API-first 架構 draft → - 14:32 — 完成了 API-first 架構 draft #worklog
note mode
Config (.obsidian.yaml):
vault: <VAULT_NAME>
note:
default_folder: Inbox
filename_strategy: title # title | slug | timestamp-title
-
Parse input:
title— required, first non-flag text.--folder <path>— override default folder (vault-relative, reject leading/or..).--tag <tag>— repeatable, adds to frontmatter.- Trailing text after flags — optional initial body.
-
Compute filename by kebab-casing the title (lowercase, whitespace/punctuation →
-, collapse repeats). Keep Unicode characters intact.title→<kebab>.mdslug→<kebab>-YYYYMMDD.mdtimestamp-title→YYYYMMDD-<kebab>.md
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 · 69 lines · 84 tokens per session scan A 4d6db82350b3
jot is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 848 once invoked, about $0.0004 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…