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/romkey/I2C-DirectoryWrote 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/romkey/i2c-directory/docker-ci)<a href="https://agentmods.dev/rules/romkey/i2c-directory/docker-ci"><img src="https://agentmods.dev/badge/rules/romkey/i2c-directory/docker-ci/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/romkey/i2c-directory/docker-ci"><img src="https://agentmods.dev/badge/rules/romkey/i2c-directory/docker-ci.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.00615 |
| Opus 5.5 | $0.00000 | $0.00246 |
| Sonnet 5.5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
docker-ci 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker and CI
Docker
- Base image:
ruby:4.0.5-slimwith multi-stage build - Node: 24.x for asset compilation in production Dockerfile
- Yarn: Use
yarn install --immutablein production builds - Assets: Precompiled with
SECRET_KEY_BASE_DUMMY=1 - Runtime: Non-root
railsuser; entrypoint atbin/docker-entrypoint - Version: Pass
APP_VERSIONbuild arg from git tag in release workflow
docker-compose (split stacks)
Use -f docker-compose.<stack>.yml; each stack sets a top-level name: so volumes and networks do not collide.
| File | Purpose |
|---|---|
docker-compose.dev.yml |
Local dev: Postgres + Redis + web + sidekiq. Postgres host port 5432. |
docker-compose.test.yml |
Tests: thin Ruby image, bind-mounted app, cached Bundler volume; Postgres + Redis + test service. |
docker-compose.lint.build.yml |
Lint stack with build: for Dockerfile.rubocop. |
docker-compose.lint.yml |
RuboCop using prebuilt links_rubocop:latest. |
docker-compose.server.yml |
Prod/staging-style: external Postgres via DATABASE_URL; includes Redis for Sidekiq. |
- Dev startup:
bin/devrunsdb:prepare db:seedand clears stale PIDs before starting the server - Tests:
docker compose -f docker-compose.test.yml run --rm test - Lint (quick):
docker compose -f docker-compose.lint.yml run --rm rubocop - Lint (build):
docker compose -f docker-compose.lint.build.yml run --rm rubocop - Server migrate:
docker compose -f docker-compose.server.yml --profile tools run --rm migrate
GitHub Actions
- ci.yml: Push/PR to
mainandstaging; PostgreSQL 16 and Redis 8 services; runs Brakeman, bundler-audit, RuboCop, andbin/rails test - staging.yml: Push to
staging; tests then builds/pushes:stagingimage toghcr.io - release.yml: Push tag
v*; tests then builds/pushes semver +:latestimages withAPP_VERSIONfrom tag - Uses
ruby/setup-rubywith bundler-cache andactions/setup-nodewith yarn cache - Concurrency: cancels in-progress runs for the same ref
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 · 43 lines · 0 tokens per session scan A 7ec394d58cd1
docker-ci is a cursor rule published in the GitHub repository romkey/I2C-Directory (11 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 615 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-30.
Other cursor rules, from other repositories
fix-bugs
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
devops
DevOps Engineer - Docker, CI/CD, Cloud Deployment.
deployment-engineer-intelligent
CI/CD and deployment automation specialist for containerized applications. Apply this rule when configuring CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins), creating Docker containers with multi-stage builds, setting up Kubernetes deployments and services, implementing Infrastructure as Code, configuring…
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.