Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bleszily/runcanonnpx agentmods add rules/bleszily/runcanon/docker-rebuildWrote 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/bleszily/runcanon/docker-rebuild)<a href="https://agentmods.dev/rules/bleszily/runcanon/docker-rebuild"><img src="https://agentmods.dev/badge/rules/bleszily/runcanon/docker-rebuild/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/bleszily/runcanon/docker-rebuild"><img src="https://agentmods.dev/badge/rules/bleszily/runcanon/docker-rebuild.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.00277 | $0.00277 |
| Opus 5.5 | $0.00111 | $0.00111 |
| Sonnet 5.5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
docker-rebuild 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
Docker rebuild after code changes
When you modify any application or package code in this repo (TypeScript, Svelte, platform, core, CLI, MCP, Dockerfiles, or demo scripts), you must rebuild the demo image and restart the container before telling the user the work is done.
Do this automatically — never wait for the user to ask.
Command
bash scripts/demo-docker.sh
Run from the repo root. Allow up to ~2 minutes for the build to finish.
What this preserves
- Container name:
runcanon-demo - URL: http://127.0.0.1:3000
- Data volume
runcanon-datapersists across rebuilds
When to rebuild
- After any code edit that affects dashboard, platform, core, CLI, or MCP behavior
- After adding or changing API routes, import logic, org admin features, or UI components
- Do not skip rebuild because the change "seems small"
After rebuild
Briefly confirm in your response that the image was rebuilt and the container restarted (include container name and that http://127.0.0.1:3000 is serving the new 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 First seen · 35 lines · 277 tokens per session scan A 59b3d097cf0e
docker-rebuild is a cursor rule published in the GitHub repository bleszily/runcanon (5 stars, last pushed 19d ago), licensed MIT. It adds 277 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-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.
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.
container-rightsizer
Rightsizes container CPU and memory requests and limits using real usage data. Reduces requested resources without hitting OOMKills or CPU throttling.