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/waitlist-implementation)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/waitlist-implementation"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/waitlist-implementation/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/waitlist-implementation"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/waitlist-implementation.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.01098 |
| Opus 5.5 | $0.00000 | $0.00439 |
| Sonnet 5.5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
waitlist-implementation 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Waitlist Implementation Guide
Overview
Shipkit includes a complete waitlist feature for product launches. The implementation follows Next.js App Router patterns with Server Components, Server Actions, and Drizzle ORM.
Architecture Pattern
Service Layer Pattern
The waitlist uses individual async functions instead of classes due to Next.js "use server" restrictions:
- ✅ Correct: Individual exported async functions in waitlist-service.ts
- ❌ Incorrect: Class-based services (not allowed in "use server" files)
Database Schema
The waitlist table is defined in schema.ts with:
- Email uniqueness constraints
- Proper indexing for performance
- Timestamp tracking for analytics
- Metadata field for extensibility
File Structure
Core Components
- Main Page: waitlist/page.tsx - Server component with Suspense
- Hero Component: waitlist-hero.tsx - Client component with form
- Admin Dashboard: admin/waitlist/page.tsx - Server component
Service Layer
- Database Operations: waitlist-service.ts - Individual async functions
- Server Actions: waitlist-actions.ts - Form handling and email integration
Key Functions
// Service functions (use server)
addWaitlistEntry() - Add new entry to database
isEmailOnWaitlist() - Check for duplicates
getWaitlistEntries() - Paginated retrieval
getWaitlistStats() - Analytics data
// Server actions (use server)
addToWaitlist() - Full signup flow with email
addToWaitlistSimple() - Quick email signup
getWaitlistStats() - Public stats access
Database Patterns
Migration Pattern
Use Drizzle Kit for schema changes:
bun run db:push
Schema Conventions
- Use
createTablewith DB_PREFIX from env - Include proper indexes for query patterns
- Use timestamps for audit trails
- Store metadata as JSON string
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 · 165 lines · 0 tokens per session scan A eb1a29d486ae
waitlist-implementation 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 1,098 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.
waitlist-implementation compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| waitlist-implementationlacymorrow/paperclip-hub | Cursor rule | 15 | yesterday | MIT | A | 0 | Cursor |
| server-actionskrivoox/agent-stack-template | Cursor rule | 30 | 1mo ago | MIT | A | 0 | Cursor |
| repository-class-conventionsWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 149 | Cursor |
| payload-configurationshipkit-io/bones | Cursor rule | 21 | yesterday | none | A | 0 | Cursor |
| convex-development---generalWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 84 | Cursor |
| graceful-degradationshipkit-io/bones | Cursor rule | 21 | yesterday | none | A | 0 | Cursor |
| convex-schema-design---example-schemaWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 75 | Cursor |