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/environment)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/environment"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/environment/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/environment"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/environment.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.00401 |
| Opus 5.5 | $0.00000 | $0.00160 |
| Sonnet 5.5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
environment 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
Environment Configuration Best Practices
Environment Files
- Use
.env.localfor local development - Use
.env.developmentfor development - Use
.env.testfor testing - Use
.env.productionfor production - Never commit env files
- Document all variables
- Use example files
Variable Naming
- Use SCREAMING_SNAKE_CASE
- Use descriptive names
- Group related variables
- Use proper prefixes
- Document purpose
- Consider scope
- Maintain consistency
Security
- Never commit secrets
- Use proper encryption
- Rotate secrets regularly
- Use secret management
- Audit access
- Monitor usage
- Document procedures
Validation
- Validate at startup
- Check required variables
- Validate formats
- Type checking
- Document requirements
- Handle missing values
- Log validation errors
Organization
- Group by purpose
- Use proper prefixes
- Document structure
- Maintain consistency
- Version control
- Review regularly
- Keep organized
Development
- Use local overrides
- Document setup
- Share examples
- Handle conflicts
- Maintain parity
- Test configurations
- Document workflows
Production
- Use proper secrets
- Configure monitoring
- Set up logging
- Handle rotation
- Plan for scaling
- Document deployment
- Regular audits
Testing
- Use test-specific values
- Mock when needed
- Clean up after tests
- Validate configurations
- Document test setup
- Maintain isolation
- Regular validation
Documentation
- Document all variables
- Explain purpose
- Show examples
- Document requirements
- Keep updated
- Version control
- Regular reviews
Management
- Use secret management
- Configure access control
- Monitor usage
- Regular rotation
- Audit access
- Document procedures
- Plan for emergencies
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 e0c47e95d6d1
environment 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 401 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.
environment compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| environmentlacymorrow/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 |