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/security)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/security"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/security/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/security"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/security.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.00508 |
| Opus 5.5 | $0.00000 | $0.00203 |
| Sonnet 5.5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
security 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Best Practices
Authentication
- Implement proper auth flow
- Use secure sessions
- Handle password security
- Implement MFA
- Manage JWT securely
- Monitor auth attempts
- Regular security audits
Authorization
- Implement role-based access
- Use proper middleware
- Validate permissions
- Handle edge cases
- Monitor access patterns
- Regular access reviews
- Document policies
Data Protection
- Encrypt sensitive data
- Use proper hashing
- Implement data masking
- Handle PII properly
- Regular security scans
- Monitor data access
- Document procedures
API Security
- Validate all inputs
- Use rate limiting
- Implement CORS properly
- Use proper headers
- Monitor API usage
- Regular security tests
- Document endpoints
Webhook Security
- ALWAYS verify webhook signatures using timing-safe comparison
- Never accept webhooks without proper signature validation
- Use environment variables for webhook secrets
- Implement idempotency using unique event identifiers
- Validate all webhook payload fields before processing
- Never log sensitive data from webhook payloads
- Return proper HTTP status codes for webhook responses
- Implement rate limiting per webhook source
- Process webhooks asynchronously when possible
- Use database transactions for webhook data consistency
Frontend Security
- Prevent XSS attacks
- Handle CSRF properly
- Secure form submissions
- Validate client input
- Monitor client security
- Regular security audits
- Document measures
Backend Security
- Validate all inputs
- Use proper sanitization
- Handle file uploads securely
- Implement proper logging
- Monitor server security
- Regular security scans
- Document procedures
Infrastructure
- Use proper firewalls
- Implement WAF
- Configure security groups
- Monitor infrastructure
- Regular security audits
- Document architecture
- Plan for incidents
Compliance
- Follow security standards
- Implement compliance
- Regular audits
- Document procedures
- Monitor compliance
- Keep records
- Regular reviews
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 · 110 lines · 508 tokens per session scan A 2c6cfb8e3f2c
security 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 508 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.
security compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| securitylacymorrow/paperclip-hub | Cursor rule | 15 | yesterday | MIT | A | 0 | Cursor |
| always-push-pritsmemeworks/adhx | Cursor rule | 19 | 5d ago | MIT | A | 279 | Cursor |
| codex-premium-website-skillsTheGoat395/Codex-Skills | Cursor rule | 137 | 20d ago | MIT | A | 0 | Cursor |
| context-managementvibestackdev/vibe-stack | Cursor rule | 8 | yesterday | MIT | A | 0 | Cursor |
| project-contextvibestackdev/vibe-stack | Cursor rule | 8 | yesterday | MIT | A | 508 | Cursor |
| typescript-coding-styleWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 128 | Cursor |
| javascript-typescript-code-styleWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 88 | Cursor |