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/jumpstarter-dev/jumpstarter/jep-processgit clone --depth 1 https://github.com/jumpstarter-dev/jumpstarterWhat 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.00000 | $0.00584 |
| Opus 5 | $0.00000 | $0.00292 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
jep-process 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JEP Process
This rule helps with creating Jumpstarter Enhancement Proposals (JEPs).
When to Use
- JEP: Cross-cutting changes that affect multiple components, change public APIs or protocols, or require community consensus.
Creating a JEP
-
Choose the next JEP number: Look at existing files in
docs/source/contributing/jeps/and pick the next available incrementing integer. JEP-0000 through JEP-0009 are reserved for process/meta-JEPs, so start from JEP-0010 for regular proposals. -
Create the file: Copy the template from
docs/source/contributing/jeps/JEP-NNNN-template.mdtodocs/source/contributing/jeps/JEP-NNNN-short-title.md, replacingNNNNwith the zero-padded number andshort-titlewith a descriptive slug. -
Fill in the metadata table:
- Set the JEP number (incrementing integer, NOT the PR number)
- Set the title, author(s) with GitHub handle and email
- Set the type:
Standards Track,Informational, orProcess - Set the status to
Draftinitially, thenDiscussionwhen the PR is ready for review - Set the created date to today
-
Fill in all mandatory sections:
- Abstract (3-5 sentences)
- Motivation (concrete problem description)
- Proposal (written as if teaching the feature)
- Design Decisions (use DD-N pattern with alternatives and rationale)
- Design Details (architecture, data flow, error handling)
- Test Plan (unit, integration, HiL, manual)
- Backward Compatibility
- Consequences (positive and negative)
- Rejected Alternatives
-
Open a PR against main with the
jeplabel.
Design Decision Format (DD-N)
JEPs use this format for individual decisions:
### DD-N: Decision title
**Alternatives considered:**
1. **Option A** - Brief description.
2. **Option B** - Brief description.
**Decision:** Option A.
**Rationale:** Explain why this option was chosen.
Key Rules
- JEP numbers are incrementing integers, NOT derived from PR numbers
- JEPs live in
docs/source/contributing/jeps/ - All JEPs should be merged as PRs so the documentation is part of the Jumpstarter docs/source
- Rejected JEPs are normally not merged, but can be merged with "Rejected" status if there is an architectural reason to preserve them
- The license for all documents is Apache-2.0
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 · 63 lines · 0 tokens per session scan A 5331e0677424
jep-process is a cursor rule published in the GitHub repository jumpstarter-dev/jumpstarter (214 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 584 tokens. 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 cursor rules, from other repositories
chiplab
Repository agent instructions for chiplab.
open-locker-domain
This project implements a digital locker sharing system for lending physical items. Follow these domain-specific conventions.
monorepo-architecture
This is a monorepo containing multiple interconnected components for the Open-Locker IoT system.
scramble-openapi
REST API OpenAPI Documentation Guidelines.
adr-decision-required
Require ADRs for architecture-significant decisions.
modbus-integration
The backend does not communicate with Modbus hardware directly. Physical locker control runs in locker-client (Raspberry Pi), which talks to hardware via Modbus and reports status back to the backend over MQTT.