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.
npx agentmods add skills/ayimmam/pcic/project-setupnpx skills add ayimmam/PCIC --skill project-setupgit clone --depth 1 https://github.com/ayimmam/PCICWhat 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 | $0.00035 | $0.00461 |
| Opus 5 | $0.00017 | $0.00230 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
project-setup 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 2d 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
PCIC Project Setup Guide
Prerequisites
- Node.js 18+ and npm
- MongoDB (local install or MongoDB Atlas account)
- Git
Quick Setup
# 1. Clone the repo
git clone <repo-url>
cd PCIC-Management-System
# 2. Install dependencies
cd client && npm install
cd ../server && npm install
# 3. Configure environment
cd ../server
cp .env.example .env
# Edit .env with your MongoDB URI and JWT secret
# 4. Create the uploads directory
mkdir uploads
# 5. Seed an admin user (optional)
node src/seed.js
# 6. Run both services
# Terminal 1:
cd server && npm run dev
# Terminal 2:
cd client && npm run dev
Environment Variables (server/.env)
| Variable | Required | Description |
|---|---|---|
MONGODB_URI |
Yes | MongoDB connection string |
JWT_SECRET |
Yes | Random string for signing tokens |
PORT |
No | Server port (default: 5000) |
SMTP_HOST |
No | Email SMTP host |
SMTP_PORT |
No | Email SMTP port |
SMTP_USER |
No | Email sender address |
SMTP_PASS |
No | Email app password |
SMTP variables are optional — emails are skipped if not configured.
URLs
- Frontend: http://localhost:5173
- Backend API: http://localhost:5000/api
- Health check: http://localhost:5000/api/health
Troubleshooting
- CORS errors: The Vite dev server proxies
/apito port 5000 — make sure the server is running. - Auth errors: Clear
pcic_tokenfrom localStorage and re-login. - MongoDB connection: Ensure your
MONGODB_URIis correct and MongoDB is running.
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.
- 2d ago First seen · 68 lines · 35 tokens per session scan A 4c672dee7c24
project-setup is a skill published in the GitHub repository ayimmam/PCIC (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 461 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…