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/backend-express)<a href="https://agentmods.dev/rules/ayimmam/pcic/backend-express"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/backend-express/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/backend-express"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/backend-express.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.00497 |
| Opus 5.5 | $0.00000 | $0.00199 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
backend-express 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
Backend Conventions
Architecture (routes → controllers → models)
server/src/routes/feature.js — Route definitions, middleware attachment
server/src/controllers/featureController.js — Business logic, request/response
server/src/models/Feature.js — Mongoose schema & model
server/src/middleware/ — auth.js (JWT), roleGuard.js (role check)
server/src/utils/ — email.js, upload.js
Patterns
- ES modules — use
import/export, every file uses.jsextension in imports - Route files use
Router()from Express, exported as default - Controllers are named exports:
export const getItems = async (req, res) => {} - Always wrap controller logic in try/catch, return
res.status(code).json({ message }) - Use
req.user(set by auth middleware) for the authenticated user - Role checks:
roleGuard("president", "pm")— pass allowed roles as arguments
Mongoose Models
- Schema defined with
new mongoose.Schema({...}, { timestamps: true }) - Passwords hashed in
pre("save")hook with bcryptjs - Refs use
mongoose.Schema.Types.ObjectIdwithref: "ModelName" - Subdocuments for embedded arrays (e.g., attendees in Event, timeline in Decision)
API Route Prefix
All routes mounted under /api/:
/api/auth— login, register, me/api/events— CRUD + checkin/api/members— list, count, status change/api/decisions— CRUD with filters/api/strikes— list, member strikes, summary, assign/api/candidates— list, submit (multipart), approve, reject
Auth Flow
- Client sends
POST /api/auth/loginwith email + password - Server returns
{ token, user }— JWT valid for 7 days - Client stores token in localStorage, attaches via axios interceptor
- All protected routes use
authmiddleware → setsreq.user - Role-restricted routes add
roleGuard(...)afterauth
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 · 52 lines · 0 tokens per session scan A c3dbbae0158b
backend-express 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 497 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
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.