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/mamahoos/dot-filesWrote 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/mamahoos/dot-files/00-user-context)<a href="https://agentmods.dev/rules/mamahoos/dot-files/00-user-context"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/00-user-context/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/mamahoos/dot-files/00-user-context"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/00-user-context.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.01498 | $0.01498 |
| Opus 5.5 | $0.00599 | $0.00599 |
| Sonnet 5.5 | $0.00300 | $0.00300 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade B, and why
00-user-context scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Never casually suggest disabling security controls or firewall rules, exposing services publicly, credentials in source, running as root, `chmod 777`, or bypassing certificate verification. Label any security-weakening w How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Context — mamahoos
Identity
mamahoos on GitHub and Telegram; use that name in technical contexts. Computer Engineering student working in DevOps / Infrastructure / Platform Engineering. Programming since 2020.
Workspace layout
~/dev/personal/ = active repos; work/ = employer repos; vendor/ = third-party clones. desk/ is the live workbench: config/ (sensitive), runbooks/ (operations), deploy/ (bundles), knowledge/ (learning), inbox/ (temporary). archive/ is frozen projects and artifacts.
Technical profile
Strongest in Python and DevOps/infrastructure.
- Python stack: type hints and strict typing,
mypy, Pydantic, FastAPI, SQLAlchemy, Alembic, async Python, PostgreSQL, Redis. - Platform: Linux administration, Bash, networking, Git/GitHub/GitLab, GitHub Actions and self-hosted runners, Docker and Compose, Traefik, Nginx, Prometheus, Grafana, Graylog, UFW, SSH, DNS, VMware ESXi, Ansible, Terraform, Kubernetes, Helm, GitOps/ArgoCD, OpenTelemetry.
Actively deepening: Linux → Networking → Kubernetes → Helm → Terraform → GitOps → Observability → Security → Platform Engineering.
Familiarity is not mastery. That list is not uniform expertise — separate what they use confidently, what they are learning, and what they have only met conceptually. For a technology they are learning, teach the underlying model; do not re-explain programming basics they clearly know.
Engineering preferences
Optimize in this order: maintainable, explicit, strongly typed, modular, testable, observable, secure by default, easy to operate, easy to extend. Production-oriented over clever or compact.
Avoid unnecessary abstractions, premature frameworks, magic behavior, duplicated configuration, weak typing where strong typing is practical, monolithic modules, hard-coded infrastructure values, and anything that only works on the author's machine.
State meaningful trade-offs briefly instead of silently picking a side.
Python
Modern Python, extensive type hints, strict typing, APIs designed around clear types and contracts. Pydantic for runtime validation; dataclasses / TypedDict / Protocol where they fit. Avoid Any without a concrete reason. Async when the surrounding architecture is async. Clean module boundaries, business logic independent of infrastructure, dependency injection when it buys testability. Do not overengineer simple code.
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 Changed · +4 lines · +91 tokens per session aed83766bb8b
- 1mo ago First seen · 101 lines · 1,407 tokens per session scan B 683f7bd8f3e6
00-user-context is a cursor rule published in the GitHub repository mamahoos/dot-files (5 stars, last pushed yesterday), licensed MIT. It adds 1,498 tokens to every session, about $0.0060 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other cursor rules, from other repositories
kolor
Ulubiony kolor użytkownika.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.