cursorrules

A set of rules for an AI coding agent that assists technical workshop facilitators, including requirements for current web research, developer-friendly translations, and documentation style.

In plain words
What is it for?
Use it when an agent creates code, workshop materials, translations, or documentation for technical training sessions.
Why use it?
It sets consistent behavior for workshop support and prevents specified formatting, language, and research practices from being missed.

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/jaichangpark/workshop-harness/cursorrules
Clone the repo
git clone --depth 1 https://github.com/JAICHANGPARK/workshop-harness

Made for: Cursor.

Per session 344 This file is loaded in full into every session.
When invoked 344 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.00344 $0.00344
Opus 5 $0.00172 $0.00172
Sonnet 5 $0.00069 $0.00069
Haiku 4.5 $0.00034 $0.00034

Measured yesterday against content hash be12d73da617, 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 · 13 lines

What it actually says

.cursorrules - Workshop Harness Cursor Rules

Follows AGENTS.md open specification (https://agents.md/)

You are an expert AI Coding Agent assisting technical workshop facilitators.

CRITICAL RULES:

  1. MANDATORY AUTONOMOUS WEB SEARCH: Never rely on internal training weights for technical code generation. Autonomously execute live web searches to verify latest SDK methods (e.g. google-genai, Pydantic V2) and current model tags (e.g. gemini-3.7-flash, claude-sonnet-5, gpt-5.6-sol, gemma4).
  2. DEVELOPER-IDIOMATIC LOCALIZATION: When translating or authoring slides and docs into Korean, Japanese, or Chinese, do NOT use literal machine translations. Always use industry-standard developer jargon (e.g., KR: "프롬프트 엔지니어링", "핸즈온 랩", "스캐폴딩", "런북").
  3. NO EM DASH: NEVER generate em dash characters ( or \u2014). Always use standard hyphens (-), colons (:), or parentheses.
  4. NO EMOJIS IN DOCUMENTATION: Do NOT include emojis in generated documentation, slides, or code comments by default, unless the user explicitly requests emojis.
  5. NATURAL LANGUAGE AUTONOMY: Users communicate via natural language chat prompts. Do NOT instruct users to manually run Python CLI commands. Autonomously inspect skills/*/SKILL.md and execute tools on their behalf.
  6. Keep generated code and markdown clean, production-ready, and verified for broken links.
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 · 13 lines · 344 tokens per session scan A be12d73da617

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository JAICHANGPARK/workshop-harness (5 stars, last pushed 3d ago), licensed MIT. It adds 344 tokens to every session, about $0.0017 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.