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/ayimmam/PCICWrote 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/ayimmam/pcic/mongoose-models)<a href="https://agentmods.dev/rules/ayimmam/pcic/mongoose-models"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/mongoose-models/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/ayimmam/pcic/mongoose-models"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/mongoose-models.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.00443 |
| Opus 5.5 | $0.00000 | $0.00177 |
| Sonnet 5.5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
mongoose-models 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 2mo ago.
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
Mongoose Model Reference
Existing Models
User — name, email, password, role, batch, domain, status
- role: president | vice_president | secretary | pm | pr | mc | event_organizer | domain_leader | member
- batch: batch_1 | batch_2 | batch_3
- domain (PCIC domain only): Code Crafters | Turing Tribe | Cyber Crew | Pixel Peeps
- status: active | warning | inactive
Event — title, description, date, domain, capacity, createdBy, attendees[]
- attendees subdoc:
{ memberId, checkedIn, checkedInAt }
Decision — title, description, category, status, startDate, endDate, stakeholders[], author, timeline[], actionItems[]
- category: exam-schedule | holiday | stakeholder | project-progress | learning
- status: pending | approved | implemented
- startDate/endDate: optional; required for exam-schedule (both), holiday (at least startDate)
- timeline subdoc:
{ status, changedBy, changedAt, notes } - actionItems subdoc:
{ task, assignee (ref User), dueDate, status (pending | done) } - GET /api/decisions/conflicts?date=YYYY-MM-DD returns exam-schedule and holiday decisions overlapping that date
Strike — memberId, reason, assignedBy (timestamps auto)
Candidate — name, email, motivation, portfolioUrl, resumeUrl, status, reviewedBy, reviewedAt
- status: pending | approved | rejected
When Adding New Models
- Create in
server/src/models/ModelName.js(PascalCase) - Always include
{ timestamps: true }option - Use enums for fixed-value fields
- Add a controller in
server/src/controllers/ - Add routes in
server/src/routes/, mount inserver/src/index.js
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.
- 2mo ago First seen · 40 lines · 0 tokens per session scan A ff1314db6131
mongoose-models is a cursor rule published in the GitHub repository ayimmam/PCIC (3 stars, last pushed 19d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 443 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-08-31.
Other cursor rules, from other repositories
mongo-no-obsolete-commands
Use MongoDB aggregate instead of the obsolete find/findOne commands.
fh
A set of project rules for maintaining the FeHelper Chrome extension. It describes the extension's folders, coding conventions, module structure, security expectations, analytics server, and MongoDB storage.
cursorrules
// ✅ Correct import { Model } from '@eloquentjs/core' import { v } from '@eloquentjs/validator' import User from './models/User.js'.
windsurfrules
Node.js ESM + EloquentJS ORM + PostgreSQL/MongoDB + Express/Fastify.
cpp-api-patterns
Result , BSON, and MongoDB C++ API patterns (zero-error).
fastapi_endpoint_tracking_with_mongodb
Complete guide for implementing FastAPI endpoint tracking with MongoDB storage and analytics.