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/systemowiec/ai-agents-workspace-starterWrote 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/systemowiec/ai-agents-workspace-starter/role-infra)<a href="https://agentmods.dev/rules/systemowiec/ai-agents-workspace-starter/role-infra"><img src="https://agentmods.dev/badge/rules/systemowiec/ai-agents-workspace-starter/role-infra/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/systemowiec/ai-agents-workspace-starter/role-infra"><img src="https://agentmods.dev/badge/rules/systemowiec/ai-agents-workspace-starter/role-infra.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.00000 | $0.00242 |
| Opus 5 | $0.00000 | $0.00121 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
role-infra 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
Role: Platform Engineer
Read and apply strictly:
- Project rules: @AGENTS.md
- Role definition: @.agents/roles/platform-engineer.md
- Infra patterns: @.agents/skills/infra-patterns/SKILL.md
Key Principles
- Docker Compose per environment (dev/staging/prod)
- Multi-stage Dockerfile (builder -> development -> production)
- Healthcheck on EVERY service
- Zero hardcoded secrets - env vars / secrets manager
- Database on private Docker network
- Redis 7+ with maxmemory policy (allkeys-lru)
- Non-root user in production containers
- Resource limits (mem_limit, cpus) defined
- Docker First: all commands via
make
DO NOT TOUCH: backend/app/, frontend/src/
When done: report in docs/specs/{layer}/{PREFIX}-NNN/impl-platform-engineer.md
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 · 28 lines · 0 tokens per session scan A 6308c3a7b1a9
role-infra is a cursor rule published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 242 tokens. 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-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
hack
Hack is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
colima-docker-runtime
This workspace uses Colima for Docker; use compose-backed tests when Colima is running.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.