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.
npx agentmods add rules/cadasto/openehr-assistant-mcp/docker-workflowgit clone --depth 1 https://github.com/Cadasto/openehr-assistant-mcpWrote 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/cadasto/openehr-assistant-mcp/docker-workflow)<a href="https://agentmods.dev/rules/cadasto/openehr-assistant-mcp/docker-workflow"><img src="https://agentmods.dev/badge/rules/cadasto/openehr-assistant-mcp/docker-workflow.svg" alt="Measured on agentmods" 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 | $0.00326 | $0.00326 |
| Opus 5 | $0.00163 | $0.00163 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
docker-workflow 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 5d 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-only workflow for PHP/Composer
This project has no local PHP or Composer in the host (e.g. WSL). All PHP and Composer commands must run inside the dev container.
Do not run
composer ...on the hostphp ...on the hostvendor/bin/phpunit ...on the host
These will fail; use the Docker workflow below instead.
Correct commands
Start dev containers (once):
make up-dev
Install dependencies:
make install
Run tests:
docker compose -f .docker/docker-compose.yml -f .docker/docker-compose.dev.yml exec -u 1000:1000 app composer test
Run PHPStan:
docker compose -f .docker/docker-compose.yml -f .docker/docker-compose.dev.yml exec -u 1000:1000 app composer check:phpstan
Run coverage (HTML):
docker compose -f .docker/docker-compose.yml -f .docker/docker-compose.dev.yml exec -u 1000:1000 app composer test:coverage
Single test class or filter:
docker compose -f .docker/docker-compose.yml -f .docker/docker-compose.dev.yml exec -u 1000:1000 app vendor/bin/phpunit --filter SomeTest
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.
- 5d ago First seen · 50 lines · 326 tokens per session scan A 4ee4af519c06
docker-workflow is a cursor rule published in the GitHub repository Cadasto/openehr-assistant-mcp (17 stars, last pushed 28d ago), licensed MIT. It adds 326 tokens to every session, about $0.0016 per session on Opus 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-30.
Other cursor rules, from other repositories
cx-devassist-kics
Scan and remediate IaC (Infrastructure-as-Code) misconfigurations in Dockerfile, Terraform, Kubernetes YAML, and other IaC files using Checkmarx KICS and the Checkmarx MCP imageRemediation tool.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
cursorrules
When the user asks about dockerfile generator, use dockerfile-generator-ai-mcp tools: generatedockerfile, optimizelayers, validatedockerfile, suggestbaseimage.
cursorrules
When the user asks about docker helper, use docker-helper-ai-mcp tools: generatedockerfile, parsecompose, optimizeimage, securityscandata.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
about-codebase
General information about the Lineai MCP Server codebase and its purpose.