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/giselles-ai/giselleWrote 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/giselles-ai/giselle/development-guide)<a href="https://agentmods.dev/rules/giselles-ai/giselle/development-guide"><img src="https://agentmods.dev/badge/rules/giselles-ai/giselle/development-guide/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/giselles-ai/giselle/development-guide"><img src="https://agentmods.dev/badge/rules/giselles-ai/giselle/development-guide.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.00518 | $0.00518 |
| Opus 5.5 | $0.00207 | $0.00207 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
development-guide 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- development-guide — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Giselle Development Guide
Build, Test, and Lint Commands
- Build all:
pnpm build - Build specific packages:
pnpm build-sdk,pnpm build-data-type - Type checking:
pnpm check-types - Format code:
pnpm format - Development:
pnpm dev(playground),pnpm dev:studio.giselles.ai(studio) - Run tests:
pnpm -F <package> testorcd <directory> && vitest - Run specific test:
cd <directory> && vitest <file.test.ts> - Lint:
cd <directory> && biome check --write . - Format modified files:
pnpm biome check --write [filename]
Critical Requirements
- MUST run
pnpm biome check --write [filename]after EVERY code modification - All code changes must be formatted using Biome before being committed
Code Style Guidelines
- Use Biome for formatting with tab indentation and double quotes
- Follow organized imports pattern (enabled in biome.json)
- Use TypeScript for type safety; avoid
anytypes - Use functional components with React hooks
- Use Next.js patterns for web applications
- Follow package-based architecture for modularity
- Use async/await for asynchronous code rather than promises
- Error handling: use try/catch blocks and propagate errors appropriately
- Tests should follow
*.test.tsnaming pattern and use Vitest
Naming Conventions
- Files: Use kebab-case for all filenames (e.g.,
user-profile.ts) - Components: Use PascalCase for React components and classes (e.g.,
UserProfile) - Variables: Use camelCase for variables, functions, and methods (e.g.,
userEmail) - Boolean Variables and Functions: Use prefixes like
is,has,can,shouldfor clarity:- For variables:
isEnabled,hasPermission(notstatus) - For functions:
isTriggerRequiringCallsign(),hasActiveSubscription()(notrequiresCallsign()orcheckActive())
- For variables:
- Function Naming: Use verbs or verb phrases that clearly indicate purpose (e.g.,
calculateTotalPrice(), notprocess()) - Consistency: Follow these conventions throughout the codebase
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 · 43 lines · 518 tokens per session scan A 3fd1fa482697
development-guide is a cursor rule published in the GitHub repository giselles-ai/giselle (558 stars, last pushed 18d ago), licensed Apache-2.0. It adds 518 tokens to every session, about $0.0021 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
ipynb-files
This file contains rules and prompts for handling Jupyter Notebook (.ipynb) files in Cursor IDE, which currently doesn't have native support for .ipynb files.
expo
Expo Development Standards.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.