Rules for GitHub Actions, the service that automatically runs checks and deployment tasks when code changes.

Use them when changing CI or release workflows, including linting, TypeScript checks, tests, builds, dependency audits, semantic releases, and cross-platform binaries.

They make the project's automated checks and releases follow consistent commands, supported versions, operating systems, time limits, and secret requirements.

workflows — Cursor rule for Cursor by Pranav-Karra-3301: Rules for GitHub Actions, the service that automatically runs…

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/pranav-karra-3301/tuck/workflows

Clone the repo

git clone --depth 1 https://github.com/Pranav-Karra-3301/tuck

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 552 The whole file, excluding the scripts and references it only reads on demand.

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.00000	$0.00552
Opus 5	$0.00000	$0.00276
Sonnet 5	$0.00000	$0.00110
Haiku 4.5	$0.00000	$0.00055

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

Security

Grade A, and why

workflows 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 3d ago.

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/rules/workflows.mdc · 104 lines

What it actually says

Workflow Rules

CI Workflow (ci.yml)

Runs on:

Push to main
Pull requests to main

Jobs:

lint - ESLint + TypeScript checking
test - Run on Ubuntu + macOS, Node 18/20/22
build - Build and verify CLI works
security - Dependency audit

Release Workflow (release.yml)

Runs on:

Push to main (when CI passes)
Manual trigger (workflow_dispatch)

Jobs:

check - Verify releasable changes exist
release - Run semantic-release
build-binaries - Build for all platforms

Workflow Conventions

Always Use

pnpm/action-setup@v4 for pnpm
actions/setup-node@v4 for Node.js
actions/checkout@v4 for checkout
pnpm install --frozen-lockfile for deps

Version Matrix

Test on:

Node.js: 18, 20, 22
OS: ubuntu-latest, macos-latest

Timeouts

Set reasonable timeouts:

lint: 10 minutes
test: 15 minutes
build: 10 minutes
release: 20 minutes

Concurrency

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true  # For PRs
  cancel-in-progress: false # For releases

Secrets Required

GITHUB_TOKEN - Auto-provided
NPM_TOKEN - For npm publish
CODECOV_TOKEN - For coverage upload

Binary Builds

Build standalone binaries using pkg:

linux-x64, linux-arm64
darwin-x64, darwin-arm64
win32-x64

Binaries are attached to GitHub releases.

Semantic Release

Configuration in package.json:

{
  "release": {
    "branches": ["main"],
    "plugins": [
      "@semantic-release/commit-analyzer",
      "@semantic-release/release-notes-generator",
      "@semantic-release/changelog",
      "@semantic-release/npm",
      "@semantic-release/github",
      "@semantic-release/git"
    ]
  }
}

NEVER Do

Skip CI with [skip ci] in production
Hardcode secrets in workflows
Use latest tags for actions (pin versions)
Skip tests in release workflow

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.

3d ago First seen · 104 lines · 0 tokens per session scan A cf476e830435

Subscribe to this mod's changes

workflows is a cursor rule published in the GitHub repository Pranav-Karra-3301/tuck (14 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 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.

CI and CD DevOps and cloud cli dotfiles dotfiles-manager nodejs

workflows