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 skills add doug/jjj --skill publicgit clone --depth 1 https://github.com/doug/jjjWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/doug/jjj/public)<a href="https://agentmods.dev/skills/doug/jjj/public"><img src="https://agentmods.dev/badge/skills/doug/jjj/public/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/doug/jjj/public"><img src="https://agentmods.dev/badge/skills/doug/jjj/public.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00040 | $0.01644 |
| Opus 5.5 | $0.00016 | $0.00658 |
| Sonnet 5.5 | $0.00008 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
jjj 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 1mo ago.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jjj (Jujutsu Juggler)
Distributed project management and code review built on Jujutsu. No server, no database — metadata lives in an orphaned jjj bookmark and syncs with jj git push/pull.
Key insight: Jujutsu's stable Change IDs survive rebases and squashes, so metadata stays attached to work even after history rewrites.
Core Model
Problems → Solutions → Critiques
│ │ │
│ │ └── Error elimination (blocks approval)
│ └── Conjectures linked to jj Change IDs
└── Things that need solving (can nest via --parent)
State machines:
- Problems:
open→in_progress→solved/dissolved - Solutions:
proposed→submitted→approved/withdrawn - Critiques:
open→addressed/validated/dismissed
Quick Reference
| Task | Command |
|---|---|
| Initialize | jjj init |
| Status | jjj status |
| Next action | jjj next [--top N] [--mine] [--claim] |
| Interactive TUI | jjj ui |
| Sync | jjj push / jjj fetch / jjj sync |
| Full-text search | jjj search "query" |
| Timeline | jjj timeline "title" |
| File overlaps | jjj overlaps |
| Project insights | jjj insights |
Problems
| Task | Command |
|---|---|
| Create | jjj problem new "Title" [--priority critical|high|medium|low] |
| List | jjj problem list [--status open|in_progress|solved|dissolved] |
| Show | jjj problem show "title or id" |
| Tree view | jjj problem tree |
| Edit | jjj problem edit "title" --title "New" --priority high |
| Solve | jjj problem solve "title" |
| Dissolve | jjj problem dissolve "title" --reason "..." |
| Reopen | jjj problem reopen "title" |
| Sub-problem | jjj problem new "Sub" --parent "parent title" |
| Assign | jjj problem assign "title" --to [email protected] |
Solutions
| Task | Command |
|---|---|
| Create | jjj solution new "Title" --problem "title or id" |
| List | jjj solution list [--problem "title"] [--status proposed] |
| Submit for review | jjj solution submit "title" |
| Approve | jjj solution approve "title" [--rationale "..."] [--force] |
| Withdraw | jjj solution withdraw "title" --rationale "..." |
| Assign | jjj solution assign "title" --to [email protected] |
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 173 lines · 40 tokens per session scan A 3d976305c619
jjj is a skill published in the GitHub repository doug/jjj (13 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 1,644 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
meegle
A guide and command-line interface for managing Feishu/Lark Meego project data, including work items, workflow steps, views, personal tasks, and schedules. Feishu/Lark is a collaboration platform, while Meego is its project-management system.
project-ops
Use when an operator wants to run a small or mid-sized project from a flat file instead of standing up Jira or Asana — dated milestones each with one named owner and a binary done-test, rule-driven RAG status, a RAID log, slippage detection, and a two-minute weekly status report. NOT sequencing the engineering work…
kaneo-cli
Work with Kaneo tasks, projects, comments and time tracking through the kaneo CLI. Use when the user asks to list, create, update, assign or close Kaneo tasks, see what is assigned to them, comment, log time, or script against a Kaneo workspace on Kaneo Cloud or a self-hosted instance.
protocol-tracker
Internal skill for commands. The tracker verb-resolution protocol - how a lets-tracker block resolves through the active adapter, the neutral read shape, body crossing, degradation, preflight and trust. Loaded by a command or skill right before its first tracker verb. Do not trigger on user conversation.
ensemble-beads-build
Drive an existing bead hierarchy to completion through the full builder, code-review, and close pipeline (Codex skill for /ensemble:beads-build).
github-guide
Use when managing GitHub tickets, Projects kanban, pull-request delivery/review, durable issue or PR context comments, or native CI/repository enforcement on github.com or GitHub Enterprise Server. Triggers on GitHub issues, issue relationships, gh issue, Projects v2 items/Status/fields, gh project, decision or…