index

A set of project rules that points developers to the right guide for common tasks such as real-time events, API endpoints, background work, scheduled tasks, state, and authentication.

In plain words
What is it for?
Use it when building event-driven features, HTTP endpoints, background or scheduled tasks, visual flows, state management, or authenticated requests.
Why use it?
It reduces uncertainty about which instructions to follow when adding different kinds of features.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/crypticsaiyan/githubwrapped/index
Clone the repo
git clone --depth 1 https://github.com/crypticsaiyan/githubwrapped

Made for: Cursor.

Per session 253 This file is loaded in full into every session.
When invoked 253 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00253 $0.00253
Opus 5 $0.00127 $0.00127
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00025 $0.00025

Measured yesterday against content hash 90b728d6b473, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

index 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 yesterday.

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.

.cursor/index.mdc · 35 lines

What it actually says

Real time events

Make sure to use real time events guide to create a new real time event.

State/Cache management

Make sure to use state management guide to create a new state management.

Creating HTTP Endpoints

Make sure to use API steps guide to create new HTTP endpoints.

Background Tasks

Make sure to use event steps guide to create new background tasks.

Scheduled Tasks

Make sure to use cron steps guide to create new scheduled tasks.

Virtual Steps & Flow Visualization

Make sure to use virtual steps guide when connecting nodes virtually and creating smooth flows in Workbench.

Authentication

If ever need to add authentication, make sure to use middleware to authenticate the request. Make sure to use middlewares to validate the requests.

Changes

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.

  1. yesterday First seen · 35 lines · 253 tokens per session scan A 90b728d6b473

Subscribe to this mod's changes

index is a cursor rule published in the GitHub repository crypticsaiyan/githubwrapped (5 stars, last pushed 8mo ago), licensed MIT. It adds 253 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.