Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jumpstarter-dev/jumpstarternpx agentmods add rules/jumpstarter-dev/jumpstarter/creating-new-driversWrote 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/rules/jumpstarter-dev/jumpstarter/creating-new-drivers)<a href="https://agentmods.dev/rules/jumpstarter-dev/jumpstarter/creating-new-drivers"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/creating-new-drivers/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/rules/jumpstarter-dev/jumpstarter/creating-new-drivers"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/creating-new-drivers.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.00014 | $0.01404 |
| Opus 5.5 | $0.00006 | $0.00562 |
| Sonnet 5.5 | $0.00003 | $0.00281 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
creating-new-drivers 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating New Drivers
When asked to create a new driver, follow these steps:
1. Use the Driver Creation Script
Always use the provided script: ./python/__templates__/create_driver.sh
2. Required Information
Before creating a driver, ask the user for:
- Driver Package Name: The package name (e.g.,
mydriver,custom-power,device-controller)- Should be lowercase with hyphens for multi-word names
- Examples from existing drivers:
network,iscsi,ridesx,opendal,shell,gpiod,http-power,tasmota,tftp,uboot,snmp,sdwire,probe-rs,can,composite,corellium,dutlink,energenie,flashers,http,power,pyserial,qemu,ustreamer,yepkit
- Driver Class Name: The main driver class in CamelCase (e.g.,
MyDriver,CustomPower,DeviceController)- Should be descriptive and end with appropriate suffix based on functionality
- Examples:
TcpNetwork,ISCSI,RideSXDriver,Opendal,Shell,HttpPower,TasmotaPower,Tftp,UbootConsole,SNMPServer,SDWire,ProbeRs,Can,Composite,Corellium,Dutlink,EnerGenie,QemuFlasher,UStreamer,Ykush
- Author Name: Full name of the author
- Author Email: Email address of the author
3. Command Format
./python/__templates__/create_driver.sh <driver_package> <DriverClass> "<Author Name>" "<[email protected]>"
Always try to obtain the Author Name and Email from git, by checking the git configuration.
4. Examples
# Network driver
./python/__templates__/create_driver.sh network TcpNetwork "John Doe" "[email protected]"
# Power management driver
./python/__templates__/create_driver.sh custom-power CustomPowerDriver "Jane Smith" "[email protected]"
# Device control driver
./python/__templates__/create_driver.sh device-controller DeviceController "Bob Wilson" "[email protected]"
5. After Creation
Once the driver is created:
- Navigate to the new driver directory:
python/packages/jumpstarter-driver-<driver_package>/ - Register the package in the workspace by adding an entry to
python/pyproject.tomlunder[tool.uv.sources]:
Insert it alphabetically among the otherjumpstarter-driver-<driver_package> = { workspace = true }jumpstarter-driver-*entries. - Add the package to
jumpstarter-allby adding it to thedependencieslist inpython/packages/jumpstarter-all/pyproject.toml:
Insert it alphabetically among the other"jumpstarter-driver-<driver_package>",jumpstarter-driver-*entries. - Review the generated files and customize as needed
- Implement the driver logic in
driver.py - Add tests in
driver_test.py - Update the README.md with specific documentation
- Test the driver:
make pkg-test-<driver_package>
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 · 118 lines · 14 tokens per session scan A f6958bd582ab
creating-new-drivers is a cursor rule published in the GitHub repository jumpstarter-dev/jumpstarter (227 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,404 once invoked, about $0.0001 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 cursor rules, from other repositories
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.
monorepo-architecture
Open-Locker is an API-first IoT monorepo.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
n-ci_artifact
A rule for consuming CI artifacts declared by a language plugin. CI, or continuous integration, automatically checks changes; these artifacts are files or patches that the CI system materialises and verifies.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.