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/deployment)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/deployment"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/deployment/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/deployment"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/deployment.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.00635 |
| Opus 5.5 | $0.00000 | $0.00254 |
| Sonnet 5.5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
deployment 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Best Practices
Multi-Zone Deployment
Zone Deployment Strategy
- Deploy each zone as separate Vercel project
- Use consistent naming:
main-shipkit,docs-shipkit,blog-shipkit,ui-shipkit,tools-shipkit - Configure environment variables pointing to zone URLs
- Assign custom domain to main application
- Test cross-zone navigation and functionality
Zone Environment Configuration
- Main app contains zone domain environment variables
- Each zone has its own environment configuration
- Use separate databases or shared database per zone requirements
- Configure authentication to work across zones
- Set up monitoring for each zone independently
Zone-Specific Optimizations
- Documentation zone: Static generation, search optimization
- Blog zone: ISR for posts, SEO optimization
- UI zone: Component isolation, visual regression testing
- Tools zone: Client-side rendering, real-time features
Environment Setup
- Use
.env.localfor local development - Use
.env.productionfor production - Use
.env.testfor testing - Never commit environment files
- Document all required variables
- Use strong naming conventions
- Validate environment variables at startup
Docker Configuration
- Use multi-stage builds
- Optimize layer caching
- Include only necessary files
- Use appropriate base images
- Set proper environment variables
- Configure health checks
- Document all configurations
CI/CD Pipeline
- Automate build process
- Run tests before deployment
- Check code quality
- Scan for vulnerabilities
- Use proper caching
- Implement proper rollbacks
- Monitor deployment status
Production Deployment
- Use proper build optimization
- Enable proper caching
- Configure proper headers
- Set up monitoring
- Configure logging
- Set up alerts
- Plan for scaling
Infrastructure
- Use infrastructure as code
- Implement proper monitoring
- Set up logging
- Configure backups
- Plan for disaster recovery
- Document architecture
- Monitor costs
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 · 120 lines · 0 tokens per session scan A 2313fb4795c9
deployment 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 635 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.
deployment compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| deploymentlacymorrow/paperclip-hub | Cursor rule | 15 | yesterday | MIT | A | 0 | Cursor |
| vercel-cligiselles-ai/giselle | Cursor rule | 560 | yesterday | Apache-2.0 | A | 5 | Cursor |
| infrastructurefirst-fluke/fullstack-starter | Cursor rule | 226 | 2d ago | MIT | A | 0 | Cursor |
| always-push-pritsmemeworks/adhx | Cursor rule | 19 | 5d ago | MIT | A | 279 | Cursor |
| supabase-edgeshipkit-io/bones | Cursor rule | 21 | yesterday | none | A | 0 | Cursor |
| 00-cloud-agent-mandatoryfirtoz/cf-multiworker-starter-kit | Cursor rule | 11 | 20d ago | none | A | 4 | Cursor |
| aws-vpcjimmypocock/cursor-rules | Cursor rule | 8 | 1y ago | MIT | A | 6 | Cursor |