Generated Cursor rules containing project context for Kemal, a Sinatra-style web framework written in Crystal. Cursor rules give an AI coding assistant background about a repository and how its parts fit together.

Use them to give Cursor context about Kemal’s middleware pipeline, global configuration, DSL, lifecycle, and documented components.

They let the assistant use the project’s architecture and component documentation when suggesting or changing code. The marked section is regenerated, so manual edits should go outside it.

cursorrules — Cursor rule by deepfusionlabs

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/deepfusionlabs/deep-init/cursorrules

Clone the repo

git clone --depth 1 https://github.com/deepfusionlabs/deep-init

Made for: Cursor.

Per session 1,687 This file is loaded in full into every session.

When invoked 1,687 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.

Model	Per session	Once invoked
Fable 5	$0.01687	$0.01687
Opus 5	$0.00843	$0.00843
Sonnet 5	$0.00337	$0.00337
Haiku 4.5	$0.00169	$0.00169

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

Security

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

validation/end-to-end/kemal/.cursorrules · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DeepInit lean rules (Cursor)

Canonical context lives in AGENTS.md + .ai/docs/ — this file is a generated projection of the lean tier; do not edit inside the DeepInit markers (regenerated each run).

kemal — Agent Context

Kemal is a lean, Sinatra-style HTTP web framework for the Crystal language: a global-scope DSL (get "/" {... }, ws, sse, before_all, use, mount) layered over a fixed HTTP::Handler middleware chain that a single process-wide Config singleton assembles and owns.

Architecture

A composable HTTP::Handler middleware pipeline driven by a Sinatra-style global DSL over a process-global Config singleton. The whole src/kemal/ tree is loaded by three glob requires in src/kemal.cr; files reference siblings by fully-qualified constants, not per-file imports. Components map to .ai/docs/components/.

Components (7)

core — entry point + global run/stop lifecycle + the Config singleton that assembles the ordered handler chain + the top-level DSL + CLI/SSL. → .ai/docs/components/core.md
handlers — the HTTP::Handler middleware links (init, exception, head, override-method, path, static-file, filter) + the base handler with only/exclude matching. → .ai/docs/components/handlers.md
router — route storage/matching/dispatch: the terminal RouteHandler + LRU route cache, the modular Router DSL, and param parsing with body-size guards. → .ai/docs/components/router.md
websocket — real-time transports: WebSocketHandler (Origin allow-list), the WS route wrapper, and Server-Sent Events. → .ai/docs/components/websocket.md
helpers — global view/response helpers, ECR templating macros, the exception hierarchy, and path/zip utilities. → .ai/docs/components/helpers.md
logging — pluggable request-logging abstraction (deprecated in favor of stdlib Log); the default RequestLogHandler + legacy/no-op loggers. → .ai/docs/components/logging.md
ext — stdlib monkey-patches (NOT under Kemal::): reopens HTTP::Server::Context (params/redirect/route lookup + typed @store) and HTTP::Server::Response. → .ai/docs/components/ext.md

Read the full file on GitHub · 50 lines

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.

yesterday First seen · 50 lines · 1,687 tokens per session scan A d11f8640111c

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository deepfusionlabs/deep-init (6 stars, last pushed 12d ago), licensed MIT. It adds 1,687 tokens to every session, about $0.0084 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.

Testing Writing and docs agents-md ai-coding-agents ast claude-code claude-code-plugin claude-md

cursorrules

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

DeepInit lean rules (Cursor)

kemal — Agent Context

Architecture

Components (7)

What this file has done since we first saw it

Other cursor rules, from other repositories

ui

main

agent-context-doctor

frontend

cursorrules

react