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/project-overview)<a href="https://agentmods.dev/rules/ayimmam/pcic/project-overview"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/project-overview/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/project-overview"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/project-overview.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.00665 | $0.00665 |
| Opus 5.5 | $0.00266 | $0.00266 |
| Sonnet 5.5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
project-overview scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- API calls go through `client/src/api/axios.js` (auto-attaches JWT) How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCIC Internal Management System
Web platform for the Peak Craft Informatics Community (800+ students across IS, CS, IT at Hawassa University). Digitizes membership tracking, event attendance, leadership decisions, and disciplinary workflows.
Monorepo Layout
client/ — React 18 (JSX, NOT TypeScript) + Vite + Shadcn UI + Tailwind CSS
server/ — Node.js + Express.js + Mongoose (ES modules)
Tech Stack (do NOT deviate)
- Frontend: React 18, Vite, JSX (no .tsx/.ts), Shadcn UI, Tailwind CSS, React Router v6, TanStack React Query v5, react-hook-form + zod, Sonner toasts, Lucide icons
- Backend: Express.js, Mongoose ODM, JWT auth (jsonwebtoken + bcryptjs), Multer uploads, Nodemailer emails
- Database: MongoDB
- Path alias:
@/maps toclient/src/via jsconfig.json
Feature Modules (Phase 2 MVP)
| ID | Feature | Frontend Page | Backend Route |
|---|---|---|---|
| F-001 | Event Attendance Tracker | /events |
/api/events |
| F-012 | Centralized Decision Repo | /reports |
/api/decisions |
| F-006 | Disciplinary Strike System | /admin (strikes tab) |
/api/strikes |
| F-004 | Accelerated Entry Workflow | /career |
/api/candidates |
| — | Member Management | /members |
/api/members |
User Roles (enforced by roleGuard.js backend + RoleGate.jsx frontend)
president,vice_president,secretary— executive / org-wide duties per routepm(product manager) — manage members, change statuses, create decisionsmc(membership coordinator) — change member status, track attendancepr(public relations),event_organizer(event team) — per routedomain_leader— create events for their PCIC domain (see domains below)member— view events, check in, view own profile
PCIC domains (User.domain / Event.domain)
Only: Code Crafters, Turing Tribe, Cyber Crew, Pixel Peeps (not legacy labels like “Technical” or “General”).
Key Conventions
- All files use ES module syntax (
import/export, notrequire) - Frontend components are functional components with hooks
- API calls go through
client/src/api/axios.js(auto-attaches JWT) - Data fetching uses React Query hooks in
client/src/hooks/ - Backend follows routes → controllers → models pattern
- All API routes are prefixed with
/api/
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 · 55 lines · 665 tokens per session scan A d9650a9e664c
project-overview is a cursor rule published in the GitHub repository ayimmam/PCIC (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 665 tokens to every session, about $0.0027 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Search dreamd at the start of a task and quote a hit. Append when the user corrects you or states a decision.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.