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/jj-workflownpx skills add musingfox/cc-plugins --skill jj-workflowgit 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.00126 | $0.01459 |
| Opus 5 | $0.00063 | $0.00730 |
| Sonnet 5 | $0.00025 | $0.00292 |
| Haiku 4.5 | $0.00013 | $0.00146 |
Grade A, and why
jj-workflow 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jj-workflow — Natural Language to jj Operations
Translate natural language VCS requests into correct jj commands when working in a Jujutsu repository.
When to Use
Use when ALL of these conditions are met:
- A
.jjdirectory exists in the project root (verify withls -d .jj 2>/dev/null) - The user describes a version control operation in natural language
- The operation maps to one or more
jjcommands
Do NOT use when:
- There is no
.jjdirectory (this is not a jj repo) - The user is explicitly asking for git commands in a non-jj context
- The user already typed the exact
jjcommand they want to run
Operation Reference
Creating and Navigating Changes
| User Intent | jj Command | Notes |
|---|---|---|
| Start new work / new change | jj new |
Creates empty change on top of current |
| New change from specific parent | jj new <rev> |
Branch from a specific revision |
| New change with multiple parents | jj new <rev1> <rev2> |
Creates a merge change |
| Go back and edit a past change | jj edit <rev> |
Moves working copy to that change |
| See what I'm working on | jj status |
Shows working copy status |
Describing and Modifying Changes
| User Intent | jj Command | Notes |
|---|---|---|
| Add/update commit message | jj describe -m "message" |
Describes current working copy |
| Describe a different change | jj describe <rev> -m "msg" |
Describe any change |
| Combine with parent | jj squash |
Squash current into parent |
| Squash specific change into another | jj squash --from <src> --into <dst> |
Flexible squash |
| Split change into two | jj split |
Interactive split |
| Split specific files out | jj split <paths> |
Split by file |
| Discard / throw away a change | jj abandon <rev> |
Remove change from history |
Rebasing and Reorganizing
| User Intent | jj Command | Notes |
|---|---|---|
| Move change to different parent | jj rebase -r <rev> -d <dest> |
Rebase single change |
| Move change and its descendants | jj rebase -s <rev> -d <dest> |
Rebase subtree |
| Move change and reparent children | jj rebase -b <rev> -d <dest> |
Rebase branch |
| Put change on top of trunk/main | jj rebase -r <rev> -d 'trunk()' |
Common rebase target |
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 · 134 lines · 126 tokens per session scan A a8886e6b7b67
jj-workflow is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 1,459 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…