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/humzakt/dev-starter-kitWrote 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/humzakt/dev-starter-kit/general)<a href="https://agentmods.dev/rules/humzakt/dev-starter-kit/general"><img src="https://agentmods.dev/badge/rules/humzakt/dev-starter-kit/general/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/humzakt/dev-starter-kit/general"><img src="https://agentmods.dev/badge/rules/humzakt/dev-starter-kit/general.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.00274 | $0.00274 |
| Opus 5.5 | $0.00110 | $0.00110 |
| Sonnet 5.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 1mo 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
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.
- 1mo ago 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 7mo ago), licensed MIT. It adds 274 tokens to every session, about $0.0011 per session on Opus 5.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
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
python-llm-ml-workflow-cursorrules-prompt-file
Cursor rules for Python LLM & ML development with workflow integration.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
python-django-general
General coding guidance for Python and Django projects, including naming, formatting, modular apps, built-in tools, and maintainable structure. Python is a programming language, and Django is a Python web framework.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.