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/vepo/issues/development-experiencegit clone --depth 1 https://github.com/vepo/issuesWhat 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.00254 | $0.00254 |
| Opus 5 | $0.00127 | $0.00127 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
development-experience 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
Development experience
Dev seed data
src/main/resources/dev-import.sql— sample users, projects, workflows, tickets.- Loaded in dev via
DatabaseDevSetupwhen%dev.quarkus.flyway.clean-at-start=true. - Personas: see docs/feature-catalog.md § Dev personas.
Every feature must be explorable locally
After adding a user-facing feature:
- Ensure dev seed or
Givenbuilders cover the happy path. - Verify in
mvn quarkus:dev— login as a dev persona and click through the flow. - Update docs/feature-catalog.md with route and steps.
Dev commands
mvn quarkus:dev # API :8080, Angular dev server :4200 via Quinoa
OpenAPI: http://localhost:8080/openapi
Safe changes to dev-import.sql
Follow dev-import-sql-safety.mdc when editing seed data.
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 · 33 lines · 254 tokens per session scan A 7f87b6dc7e0a
development-experience is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 254 tokens to every session, about $0.0013 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
project-context
EDDI Backend — AI Agent Instructions. Complete project context, architecture, and coding guidelines.
testing-visual
Source: docs/agents/testing-visual.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
com-example-service-PublicPaymentController
AI rules for com.example.service.PublicPaymentController.
front-vue-page-conventions
YiSmartCloud front-end Vue page conventions.
cursorrules
Cursor rule "cursorrules" from Forge-Space/ui-mcp, covering uiforge mcp cursor rules, environment setup, development guidelines, component library integration and figma integration.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.