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 rules/jasperfurniss/jj/cursor-rulegit clone --depth 1 https://github.com/jasperfurniss/jjWhat 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.00014 | $0.00353 |
| Opus 5 | $0.00007 | $0.00177 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
cursor-rule 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 2d 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.
What it actually says
JJ — Jira integration
JJ is a CLI tool that fetches Jira tickets and converts them to Markdown.
When the user mentions a Jira issue key (like WEB-1234, PROJ-56, etc.)
Automatically fetch the ticket by running:
jj <KEY> --pipe
Use the full markdown output as context for the conversation. Do not ask the user if they want you to fetch it — just do it.
When the user asks to list their stories / assigned tickets / current sprint
Run:
jj list --pipe
This returns tab-separated lines: KEY STATUS ASSIGNEE SUMMARY
If the user provides custom JQL, pass it:
jj list --pipe --jql "your jql here"
Other useful commands
jj sprint --pipe— Sprint overview (all team issues) grouped by statusjj sprint --by-person --pipe— Sprint overview grouped by personjj summary --pipe— Slack-formatted sprint roundup for the whole teamjj whois <name> --pipe— Issues assigned to a person in the current sprintjj search <text> --pipe— Search issues by summary text
Notes
- JJ reads credentials from
.envin its install directory, or from env vars - The
--pipeflag makes it non-interactive (no spinners, no prompts, clean stdout) - Without
--pipe, the CLI is interactive — only use--pipein agent context
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.
- 2d ago First seen · 49 lines · 14 tokens per session scan A a4803598b6a3
cursor-rule is a cursor rule published in the GitHub repository jasperfurniss/jj (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 353 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.