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.
git clone --depth 1 https://github.com/jumpstarter-dev/jumpstarterWrote 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/project-structure)<a href="https://agentmods.dev/rules/jumpstarter-dev/jumpstarter/project-structure"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/project-structure/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/project-structure"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/project-structure.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.01460 | $0.01460 |
| Opus 5.5 | $0.00584 | $0.00584 |
| Sonnet 5.5 | $0.00292 | $0.00292 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
project-structure 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Structure
This project follows a monorepo structure with a top-level pyproject.toml that manages all packages using UV workspace.
Top-Level Structure
jumpstarter/
├── python/ # Python workspace root
│ ├── pyproject.toml # Main workspace configuration
│ ├── packages/ # All Python packages
│ ├── examples/ # Example applications
├── docs/ # Documentation (Sphinx)
│ └── source/
│ └── contributing/ # JEPs (rendered as part of docs)
│ └── jeps/ # Jumpstarter Enhancement Proposals
│ └── __templates__/ # Templates for creating new drivers
├── controller/ # Controller components
├── protocol/ # Protocol definitions
└── .cursor/ # Cursor AI rules
Workspace Configuration
The project uses UV workspace for dependency management:
- Top-level
python/pyproject.toml: Defines the workspace and includes all packages - Workspace members: All packages in
python/packages/*andpython/examples/*are included - Dependency groups: Shared development dependencies (docs, dev)
- Tool configuration: Ruff, typos, coverage, pytest settings
Package Structure
Core Packages
jumpstarter/: Main library with client, config, and common functionalityjumpstarter-protocol/: gRPC protocol definitions (excluded from linting)jumpstarter-kubernetes/: Kubernetes integrationjumpstarter-testing/: Testing utilitiesjumpstarter-imagehash/: Image hashing utilities
CLI Packages
jumpstarter-cli/: Main CLI applicationjumpstarter-cli-admin/: Administrative CLI commandsjumpstarter-cli-common/: Shared CLI utilitiesjumpstarter-cli-driver/: Driver-specific CLI commands
Driver Packages
All driver packages follow the pattern jumpstarter-driver-<name>/:
jumpstarter-driver-network/: Network interface drivers (TCP, UDP, Unix, etc.)jumpstarter-driver-power/: Power management driversjumpstarter-driver-*: Various hardware-specific drivers
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 · 168 lines · 1,460 tokens per session scan A e2f22e322515
project-structure is a cursor rule published in the GitHub repository jumpstarter-dev/jumpstarter (226 stars, last pushed today), licensed Apache-2.0. It adds 1,460 tokens to every session, about $0.0058 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
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
cursor-asdd
ASDD contribution rules for this repository.
agents
Agent engineering standards — Agents (TR-SEC-003).
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
testing-ci-rule
testing-ci-rule from DaunteEth/woofi-pro-mcp.