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/add-featurenpx skills add ayimmam/PCIC --skill add-featuregit 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/skills/ayimmam/pcic/add-feature)<a href="https://agentmods.dev/skills/ayimmam/pcic/add-feature"><img src="https://agentmods.dev/badge/skills/ayimmam/pcic/add-feature.svg" alt="Measured on agentmods" 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 | $0.00049 | $0.00771 |
| Opus 5 | $0.00024 | $0.00385 |
| Sonnet 5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
add-feature 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a New Feature Module
Checklist
Copy this and track progress:
Feature: [name]
- [ ] 1. Backend model
- [ ] 2. Backend controller
- [ ] 3. Backend routes
- [ ] 4. Mount routes in server/src/index.js
- [ ] 5. Frontend React Query hook
- [ ] 6. Frontend components
- [ ] 7. Frontend page
- [ ] 8. Add route in client/src/App.jsx
- [ ] 9. Add sidebar nav item in App.jsx (if top-level page)
Step 1: Backend Model
Create server/src/models/FeatureName.js:
import mongoose from "mongoose";
const featureSchema = new mongoose.Schema(
{
// fields here
},
{ timestamps: true }
);
export default mongoose.model("FeatureName", featureSchema);
Step 2: Backend Controller
Create server/src/controllers/featureController.js with named exports:
import Feature from "../models/Feature.js";
export const getAll = async (req, res) => {
try {
const items = await Feature.find().sort({ createdAt: -1 });
res.json(items);
} catch (error) {
res.status(500).json({ message: error.message });
}
};
Step 3: Backend Routes
Create server/src/routes/feature.js:
import { Router } from "express";
import { getAll, create } from "../controllers/featureController.js";
import auth from "../middleware/auth.js";
import roleGuard from "../middleware/roleGuard.js";
const router = Router();
router.get("/", auth, getAll);
router.post("/", auth, roleGuard("president", "pm"), create);
export default router;
Step 4: Mount in server/src/index.js
import featureRoutes from "./routes/feature.js";
app.use("/api/feature", featureRoutes);
Step 5: Frontend Hook
Create client/src/hooks/useFeature.js:
import { useQuery, useMutation, useQueryClient } from "@tanstack/react-query";
import api from "@/api/axios";
export function useFeatures() {
return useQuery({
queryKey: ["features"],
queryFn: async () => { const { data } = await api.get("/feature"); return data; },
});
}
export function useCreateFeature() {
const qc = useQueryClient();
return useMutation({
mutationFn: async (payload) => { const { data } = await api.post("/feature", payload); return data; },
onSuccess: () => qc.invalidateQueries({ queryKey: ["features"] }),
});
}
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.
- 4d ago First seen · 123 lines · 49 tokens per session scan A 7885311ab184
add-feature is a skill published in the GitHub repository ayimmam/PCIC (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 771 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…