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 commands/musingfox/cc-plugins/jj-submitgit 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.00019 | $0.00632 |
| Opus 5 | $0.00010 | $0.00316 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
jj-submit 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jj-submit — Submit Workflow
Complete the current change with a description and push to remote. This is the jj equivalent of git commit + push.
Environment Detection
# Verify jj repo
if [ ! -d ".jj" ] && ! jj root 2>/dev/null; then
echo "NOT_JJ_REPO"
fi
# Check colocated
if [ -d ".git" ] || git rev-parse --git-dir 2>/dev/null; then
echo "COLOCATED"
else
echo "NATIVE_JJ"
fi
Workflow
Step 1: Show Current Diff
jj diff
If the diff is empty, inform the user there are no changes to submit and stop.
Present a brief summary of what changed (files modified/added/removed, rough scope).
Step 2: Describe the Change
If the user provided a message argument, use it:
jj describe -m "<user message>"
If no message was provided, ask the user:
- Use AskUserQuestion with a text input asking for a commit message
- Suggest a message based on the diff content
After describing, confirm:
jj log --limit 1
Step 3: Start a New Change
jj new
This moves the working copy to a fresh empty change, leaving the described change as the parent.
Step 4: Bookmark Management (if needed)
Check if the previous change (now @-) already has a bookmark:
jj bookmark list --revisions @-
If no bookmark exists and this is colocated mode:
- Ask the user if they want to set a bookmark (needed for pushing)
- Suggest a bookmark name based on the change description
- If yes:
jj bookmark set <name> -r @-
Step 5: Push (Colocated Only)
If colocated and the change has a bookmark:
jj git push
Report push result. If push fails (e.g., non-fast-forward), explain and suggest jj-sync first.
If native jj (no git), skip push and inform the user.
Output Summary
## Submit Complete
**Change**: [change ID]
**Description**: [message]
**Bookmark**: [bookmark name, or "none"]
**Pushed**: [Yes/No/N/A]
**Working copy**: [new empty change ID]
Error Handling
- Empty working copy: Inform user, suggest
jj statusto check - Push rejected: Suggest running
/jj-syncfirst to rebase onto latest trunk - Conflicts in change: Warn user and suggest resolving before submitting
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 · 106 lines · 19 tokens per session scan A 3716907d3d7e
jj-submit is a command published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 632 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.