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 adampoit/ai --skill jjgit clone --depth 1 https://github.com/adampoit/aiWrote 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/adampoit/ai/jj)<a href="https://agentmods.dev/skills/adampoit/ai/jj"><img src="https://agentmods.dev/badge/skills/adampoit/ai/jj/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/adampoit/ai/jj"><img src="https://agentmods.dev/badge/skills/adampoit/ai/jj.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00055 | $0.00943 |
| Opus 5.5 | $0.00022 | $0.00377 |
| Sonnet 5.5 | $0.00011 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
jj 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jj
Use jj for version control when a repository has a .jj/ directory or jj status succeeds.
jj status
Core Model
- There is no staging area; commands operate on the current change or selected revisions.
- The working copy is a mutable commit/change. Use
jj describeto set its message. - Change IDs are stable across rewrites; commit IDs change when contents or metadata change.
- Most history edits are safe because jj records operations in the operation log.
Inspect State
Start with these read-only commands:
jj status
jj log --limit 20
jj diff --git
Inspect a specific revision:
jj show <revset>
jj evolog -r <revset>
Useful revsets:
@: current working-copy commit@-: parent of the working-copy commit::@: ancestors of the working-copy commit@::: descendants of the working-copy committrunk(): repository trunk/main baselinemine(): changes authored by the current userconflicted(): changes with conflictsmutable(): changes that can be rewritten
Quote revsets in shell commands when they contain special characters:
jj log -r 'trunk()..@'
Make Commits
Describe the current change before creating a new one:
jj describe -m "Explain why this change exists"
jj new
Create a new change from a specific parent:
jj new <revset>
Prefer small, atomic changes. If the working copy mixes concerns, split it before describing or submitting.
jj desc is the common shorthand for jj describe; use either form consistently with nearby docs or commands.
Refine History
Move selected changes from the working copy into its parent:
jj squash
Absorb modifications into matching mutable ancestors:
jj absorb
Split a mixed change:
jj split
Split whole files or filesets non-interactively by passing paths and a message:
jj split -r @ path/to/file1 path/to/file2 -m "Move focused changes into their own commit"
jj split -r @ 'glob:src/**/*.rs' -m "Update Rust sources"
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 · 174 lines · 55 tokens per session scan A f4ab7067bed6
jj is a skill published in the GitHub repository adampoit/ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 943 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-31.
Other skills, from other repositories
wrap-phase
Wraps up a development phase by cleaning AGENTSYNC.md, summarizing work, and committing changes.
git
Unified git workflow for branch-first development: status/diff review, security-first commits, worktrees, and PR creation/review via gh. Auto-activates on: "commit", "push", "branch", "worktree", "pr", "pull request", "merge", "rebase", "git".
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
commit-with-reflection
A Git workflow that creates a Chinese-language report about debugging mistakes, investigation steps, fixes, and lessons learned, then includes that report in a commit. Git is a system for tracking changes to code.
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.