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/humzakt/dev-starter-kit/generalgit clone --depth 1 https://github.com/humzakt/dev-starter-kitWhat 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.00274 | $0.00274 |
| Opus 5 | $0.00137 | $0.00137 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
general 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.
What it actually says
Project Conventions
Language & Runtime
- Python 3.11+
- Ruff for linting and formatting (configured in pyproject.toml)
- pytest for testing
Code Style
- 120 character line length
- Double quotes for strings
- Type hints on all public function signatures
- Google-style docstrings for public functions and classes
- Specific exception handling (no bare
except:) pathlib.Pathoveros.path- f-strings over
.format()or%
Development Loop
After every code change:
- Run
ruff check --fix . && ruff format .to fix lint issues - Run
pytest tests/ -vto verify tests pass - If you changed source files in
src/, ensure corresponding tests exist intests/
Commit Messages
Use Conventional Commits: feat:, fix:, chore:, docs:, test:, refactor:, style:
Don'ts
- Don't commit .env files or secrets
- Don't add comments that merely narrate what code does
- Don't create files unless absolutely necessary — prefer editing existing ones
- Don't skip running tests after making 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.
- yesterday First seen · 36 lines · 274 tokens per session scan A 2cdc62b591c3
general is a cursor rule published in the GitHub repository humzakt/dev-starter-kit (3 stars, last pushed 6mo ago), licensed MIT. It adds 274 tokens to every session, about $0.0014 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.
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.