cursorrules

Project-specific rules for AI assistants working on the CICADA codebase. They describe the project, coding conventions, testing expectations, version updates, and release steps.

In plain words
What is it for?
Use them when editing CICADA, adding tests, updating versions, preparing releases, or following its installation and tagging process.
Why use it?
They keep code changes and releases consistent with the repository’s requirements.

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/wende/cicada/cursorrules
Clone the repo
git clone --depth 1 https://github.com/wende/cicada

Made for: Cursor.

Per session 453 This file is loaded in full into every session.
When invoked 453 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.00453 $0.00453
Opus 5 $0.00227 $0.00227
Sonnet 5 $0.00091 $0.00091
Haiku 4.5 $0.00045 $0.00045

Measured yesterday against content hash 94ba0f531a02, 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.

.cursorrules · 58 lines

What it actually says

CICADA - AI Assistant Guidelines

This file contains project-specific instructions for AI assistants working on the CICADA codebase.

Release Process

When creating a new release:

  1. Create and push the git tag:

    git tag v0.X.Y
    git push origin v0.X.Y
    
  2. Update README.md version references:

    • Search for all instances of @v0.1.1 in README.md
    • Replace with the new version tag @v0.X.Y
    • Locations to update:
      • Quick Install section (stable release command)
      • Try Before Installing section (stable release command)
      • Migration tip section
  3. Update pyproject.toml version:

    • Update the version = "0.1.1" field to match the new release
  4. Test the installation:

    uv tool install git+https://github.com/wende/[email protected]
    

Project Context

  • Language Support: Currently Elixir only. Python and TypeScript are planned.
  • Primary Installation Method: uv tool install (recommended over Python direct install)
  • Index Location: .cicada/ directory in project root

Code Style

  • Use black for Python code formatting

  • Include type hints where appropriate

  • Write tests for new features

  • Keep functions focused and modular

  • When searching through the Elixir codebase, use the cicada-mcp MCP server tools instead of grep/find commands for better accuracy and context.

  • use make to run tests

Package Management

This project uses uv as the primary Python package manager. Always use uv commands:

  • Install dependencies: uv sync
  • Add new dependencies: uv add <package-name>
  • Run commands: uv run <command>
  • Install project: uv pip install -e .
  • Tool installation: uv tool install git+https://github.com/wende/[email protected]

Never use pip directly - always use uv for all Python package management tasks.

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 · 58 lines · 453 tokens per session scan A 94ba0f531a02

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository wende/cicada (40 stars, last pushed 1mo ago), licensed MIT. It adds 453 tokens to every session, about $0.0023 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-30.