Eventyay is an open-source platform for managing events, including ticket sales and registration, speaker submissions, session schedules, videos, check-ins, badges, exhibitions, and organiser administration. Event organisers use it to run both in-person and online event workflows.
Borrowing it
Nothing to install: this file belongs to fossasia/eventyay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fossasia/eventyay/dev/.cursorrulesgit clone --depth 1 https://github.com/fossasia/eventyayWrote 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/fossasia/eventyay/cursorrules)<a href="https://agentmods.dev/rules/fossasia/eventyay/cursorrules"><img src="https://agentmods.dev/badge/rules/fossasia/eventyay/cursorrules/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/fossasia/eventyay/cursorrules"><img src="https://agentmods.dev/badge/rules/fossasia/eventyay/cursorrules.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.00115 | $0.00115 |
| Opus 5.5 | $0.00046 | $0.00046 |
| Sonnet 5.5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
cursorrules 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.
What it actually says
Cursor Rules for Eventyay
- Read
agents.mdfirst; it is the single source of truth. - Apply matching scoped rules in
.github/instructions/*.mdfor each edited file. - Keep edits minimal and in requested scope.
- Preserve core safety rules:
- Event data queries use
scope(event=event). - New imports use
eventyay.*, not legacy namespaces. - JavaScript uses external ES modules (no jQuery, no inline scripts).
- Event data queries use
Do not duplicate or override project policy in this file.
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 · 12 lines · 115 tokens per session scan A bb0d786366ea
cursorrules is a cursor rule published in the GitHub repository fossasia/eventyay (1,710 stars, last pushed today), licensed Apache-2.0. It adds 115 tokens to every session, about $0.0005 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
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).