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.
git clone --depth 1 https://github.com/greyhaven-ai/sygaldryWrote 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.
[](https://agentmods.dev/rules/greyhaven-ai/sygaldry/running-commands)<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.
<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>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.1 | $0.00515 | $0.00515 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
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.
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
uvto ensure we are properly accessing our dependencies
Environment Variables
- Always prefix commands with
doppler runwhen access to environment variables is required - Example:
doppler run python app/main.pyinstead ofpython app/main.py - For development, use:
doppler run --config dev [command] - For production, use:
doppler run --config prod [command]
Dependency Management
- Use
uvfor all Python dependency management - Use
task uv:venvto create a virtual environment - Use
source .venv/bin/activateto activate the virual environment - Use
task uv:installto install dependencies from pyproject.toml - Use
task uv:syncto sync dependencies with lockfile - Use
task uv:lockto update the project's lockfile (uv.lock) - Use
task uv:update-depsto update dependencies - Use
task uv:export-reqsto export requirements.txt
Task Runner
- Prefer using the task runner for common operations instead of direct commands
- Use
task --listto see all available tasks - Use namespaced tasks for specific operations:
task docker:*for Docker operationstask doppler:*for Doppler operationstask uv:*for UV operations
- Common tasks:
task install- Install project dependenciestask lint- Run linterstask format- Run formatterstask test- Run teststask docker:build- Build the Docker imagetask docker:up- Start the project with docker-composetask doppler:setup- Setup Doppler
Development Workflow
- Set up Doppler:
task doppler:setup - Install dependencies:
task uv:install - Run the application:
doppler run python app/main.pyor use the appropriate task
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.
- 8d ago First seen · 60 lines · 515 tokens per session scan A 5d403c2cbe29
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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.