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/lacymorrow/paperclip-hubWrote 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/lacymorrow/paperclip-hub/docker)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/docker"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/docker/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/lacymorrow/paperclip-hub/docker"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/docker.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.00407 |
| Opus 5.5 | $0.00000 | $0.00163 |
| Sonnet 5.5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
docker 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 yesterday.
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 Best Practices
Image Building
- Use multi-stage builds
- Minimize layer count
- Order layers by change frequency
- Use .dockerignore
- Cache dependencies properly
- Use specific base images
- Document build process
Base Images
- Use official images
- Use specific versions
- Keep images minimal
- Scan for vulnerabilities
- Update regularly
- Document image choices
- Consider size implications
Security
- Run as non-root
- Remove unnecessary tools
- Scan for vulnerabilities
- Use secrets management
- Update dependencies
- Follow security best practices
- Regular security audits
Configuration
- Use environment variables
- Use docker-compose
- Configure health checks
- Set resource limits
- Configure logging
- Use proper networking
- Document configuration
Development
- Use hot reloading
- Share development config
- Use volume mounts
- Configure debugging
- Use docker-compose
- Document setup steps
- Maintain parity with production
Production
- Optimize for size
- Configure for performance
- Set up monitoring
- Configure logging
- Use orchestration
- Plan for scaling
- Document deployment
Dependencies
- Cache dependencies
- Use lockfiles
- Update regularly
- Scan for vulnerabilities
- Document dependencies
- Manage versions
- Clean up unused deps
Performance
- Optimize layer caching
- Minimize image size
- Configure resource limits
- Monitor performance
- Use proper storage
- Optimize networking
- Regular maintenance
Networking
- Use proper networks
- Configure service discovery
- Set up load balancing
- Manage port mapping
- Configure DNS
- Secure communications
- Document network setup
Storage
- Use proper volumes
- Configure persistence
- Manage backups
- Clean up unused data
- Monitor usage
- Plan capacity
- Document storage setup
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.
- yesterday First seen · 97 lines · 0 tokens per session scan A 63166017705d
docker is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 407 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-11-10.
docker compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dockerlacymorrow/paperclip-hub | Cursor rule | 15 | yesterday | MIT | A | 0 | Cursor |
| always-push-pritsmemeworks/adhx | Cursor rule | 19 | 5d ago | MIT | A | 279 | Cursor |
| build-guidefirst-fluke/fullstack-starter | Cursor rule | 226 | 2d ago | MIT | C | 11 | Cursor |
| dockershipkit-io/bones | Cursor rule | 21 | yesterday | none | A | 0 | Cursor |
| 90-devops-deploymentaiagentwithdhruv/ai-dev-stack | Cursor rule | 11 | 4mo ago | MIT | A | 0 | Cursor |
| aws-ecssanjeed5/awesome-cursor-rules-mdc | Cursor rule | 3.6k | 5mo ago | CC0-1.0 | A | 2,640 | Cursor |
| codex-premium-website-skillsTheGoat395/Codex-Skills | Cursor rule | 137 | 20d ago | MIT | A | 0 | Cursor |