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/TrevorEdris/fellowship-of-the-workflowsWrote 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/trevoredris/fellowship-of-the-workflows/event-driven-conventions)<a href="https://agentmods.dev/rules/trevoredris/fellowship-of-the-workflows/event-driven-conventions"><img src="https://agentmods.dev/badge/rules/trevoredris/fellowship-of-the-workflows/event-driven-conventions/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/trevoredris/fellowship-of-the-workflows/event-driven-conventions"><img src="https://agentmods.dev/badge/rules/trevoredris/fellowship-of-the-workflows/event-driven-conventions.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.00000 | $0.01370 |
| Opus 5 | $0.00000 | $0.00685 |
| Sonnet 5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
event-driven-conventions 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 7d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 7d ago First seen · 135 lines · 0 tokens per session scan A 82ef09ceefbe
event-driven-conventions is a cursor rule published in the GitHub repository TrevorEdris/fellowship-of-the-workflows (2 stars, last pushed 2mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,370 tokens. 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-09-03.
Other cursor rules, from other repositories
api-design-dotnet
API Design for .NET — ASP.NET Core patterns, MediatR, FluentValidation, and Web API best practices. Extends core/rules/api-design.mdc with .NET-specific guidance.
api-design-typescript
API Design for TypeScript — Express, NestJS, Fastify patterns, middleware, validation, and error handling. Extends core/rules/api-design.mdc with TypeScript-specific guidance.
api-design
API design guidelines — REST principles, GraphQL patterns, versioning, pagination, error handling, documentation, security, caching, and testing. Applied when designing or reviewing API endpoints.
node-architecture
Node.js architecture guidelines — project structure, layering, hexagonal adapters, config validation, and process entry point patterns. Applied when working on Node.js service architecture and structure.
node-testing
Node.js testing guidelines — API testing with Supertest, process lifecycle testing, queue consumer testing, stream testing, and Testcontainers for real infrastructure. Applied when working with Node.js test files.
node
Node.js runtime and backend best practices — configuration, process lifecycle, API robustness, async error handling, observability, and security. Applied when working on Node.js services, CLIs, or server-side code.