running-commands

running-commands is a cursor rule for Cursor from greyhaven-ai/sygaldry. It costs 515 tokens per session, scanned A, original, MIT.

A set of project rules for running Python and FastAPI commands, managing dependencies, and loading environment variables. It specifies tools such as uv, Doppler, and Task.

In plain words
What is it for?
Installing, syncing, locking, and updating Python dependencies; creating or activating a virtual environment; and running development or production commands with the correct environment variables.
Why use it?
It reduces mistakes caused by using the wrong dependency manager or running commands without the required environment settings. It also gives the agent consistent project commands to follow.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Installing, syncing, locking, and updating Python dependencies; creating or activating a virtual environment; and running development or production commands with the correct environment variables.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/greyhaven-ai/sygaldry/running-commands
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.

Clone the repo
git clone --depth 1 https://github.com/greyhaven-ai/sygaldry

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for running-commands

README.md
[![agentmods](https://agentmods.dev/badge/rules/greyhaven-ai/sygaldry/running-commands/github.svg)](https://agentmods.dev/rules/greyhaven-ai/sygaldry/running-commands)
Your own site
<a href="https://agentmods.dev/rules/greyhaven-ai/sygaldry/running-commands"><img src="https://agentmods.dev/badge/rules/greyhaven-ai/sygaldry/running-commands/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for running-commands

Your own site · 80×15
<a href="https://agentmods.dev/rules/greyhaven-ai/sygaldry/running-commands"><img src="https://agentmods.dev/badge/rules/greyhaven-ai/sygaldry/running-commands.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 515 This file is loaded in full into every session.
When invoked 515 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00515 $0.00515
Opus 5 $0.00258 $0.00258
Sonnet 5 $0.00103 $0.00103
Haiku 4.5 $0.00052 $0.00052

Measured 8d ago against content hash 5d403c2cbe29, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

running-commands 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 8d 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/running-commands.mdc · 60 lines

What it actually says


description: Details best practices specific to Python and FastAPI implementations, including recommendations for asynchronous operations, API design, code quality, and performance improvements. globs: *.py alwaysApply: false

Running Commands

Follow these guidelines when running commands in this project:

pip Commands

  • all pip commands should be prefixed with uv to ensure we are properly accessing our dependencies

Environment Variables

  • Always prefix commands with doppler run when access to environment variables is required
  • Example: doppler run python app/main.py instead of python app/main.py
  • For development, use: doppler run --config dev [command]
  • For production, use: doppler run --config prod [command]

Dependency Management

  • Use uv for all Python dependency management
  • Use task uv:venv to create a virtual environment
  • Use source .venv/bin/activate to activate the virual environment
  • Use task uv:install to install dependencies from pyproject.toml
  • Use task uv:sync to sync dependencies with lockfile
  • Use task uv:lock to update the project's lockfile (uv.lock)
  • Use task uv:update-deps to update dependencies
  • Use task uv:export-reqs to export requirements.txt

Task Runner

  • Prefer using the task runner for common operations instead of direct commands
  • Use task --list to see all available tasks
  • Use namespaced tasks for specific operations:
    • task docker:* for Docker operations
    • task doppler:* for Doppler operations
    • task uv:* for UV operations
  • Common tasks:
    • task install - Install project dependencies
    • task lint - Run linters
    • task format - Run formatters
    • task test - Run tests
    • task docker:build - Build the Docker image
    • task docker:up - Start the project with docker-compose
    • task doppler:setup - Setup Doppler

Development Workflow

  1. Set up Doppler: task doppler:setup
  2. Install dependencies: task uv:install
  3. Run the application: doppler run python app/main.py or use the appropriate task
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. 8d ago First seen · 60 lines · 515 tokens per session scan A 5d403c2cbe29

Subscribe to this mod's changes

running-commands is a cursor rule published in the GitHub repository greyhaven-ai/sygaldry (11 stars, last pushed 3mo ago), licensed MIT. It adds 515 tokens to every session, about $0.0026 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.