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.
npx agentmods add rules/zackiles/cursor-config/create-github-actiongit clone --depth 1 https://github.com/zackiles/cursor-configWhat 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.00000 | $0.03166 |
| Opus 5 | $0.00000 | $0.01583 |
| Sonnet 5 | $0.00000 | $0.00633 |
| Haiku 4.5 | $0.00000 | $0.00317 |
Grade A, and why
create-github-action 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.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt: Implementing Multi-Purpose GitHub Actions with Deno 2
ROLE: You are an advanced code-generating LLM tasked with creating a reusable, well-tested, production-ready GitHub Action (and its supporting workflows) using Deno 2.
TASK:
-
The user has provided you information about the Github Action they'd like you to create. Think deeply about the purpose and use-case of that Github Action before starting, including reading all and any documentation or designs they've provided you. You’ll implement the functionality of their Github action using Typescript running in the Deno 2 runtime within the Github Action runner.
-
After you understand the users requirements, you will take this project's state from "new repo" → "published on the GitHub Marketplace" for any common automation scenario (CI, CD, content transformation, API-driven tasks, etc.) that the user is asking you for right now.
-
Complete each Phase listed below, PHASE BY PHASE, validating your work after each Phase, and following the requirements of each Phase meticulously; each section contains authoritative links, version numbers, and conventions you must honor and use your tools such as web search to learn more.
Phase 1 · Research & Planning
| Step | Requirements |
|---|---|
| 1 · Define scope | Pinpoint the action's purpose (build/test, deploy, docs generation, issue triage, etc.). List inputs / outputs / secrets. **Action Type Consideration:** Briefly evaluate if a Composite (running Deno scripts, good for simplicity), JavaScript (if Node.js is preferred), or Docker (for complex environments) action is the best fit before defaulting to Composite. |
| 2 · Gather refs | Save URLs: • [Actions types – Docker / JavaScript / Composite](https://github.com/actions/toolkit/blob/main/docs/action-types.md) :contentReference[oaicite:0]{index=0} • [GitHub Actions docs](https://docs.github.com/actions) :contentReference[oaicite:1]{index=1} • [Deno 2 manual](https://docs.deno.com) • [`denoland/setup-deno@v2`](https://github.com/denoland/setup-deno) :contentReference[oaicite:2]{index=2} • [`nektos/act`](https://github.com/nektos/act) :contentReference[oaicite:3]{index=3} • [`@actions/core`](https://www.npmjs.com/package/@actions/core) v1.11.1 :contentReference[oaicite:4]{index=4} |
| 3 · Architecture | Sketch folder tree: `action.yml` · `src/` · `tests/` · `.github/workflows/ci.yml` · `.devcontainer/` · `CHANGELOG.md` Enumerate dependencies—install them **before use**: ```bash |
| deno add jsr:@std/fmt/colors | |
| deno add jsr:@std/cli | |
| deno add npm:@actions/core |
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 · 276 lines · 0 tokens per session scan A 21b613139d90
create-github-action is a cursor rule published in the GitHub repository zackiles/cursor-config (17 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,166 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-08-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.