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 instructions/ayimmam/pcic/copilot-instructionsgit 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.00530 | $0.00530 |
| Opus 5 | $0.00265 | $0.00265 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
PCIC copilot-instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions — PCIC Management System
Project Context
Internal management system for the Peak Craft Informatics Community (PCIC). Monorepo with client/ (React + Vite) and server/ (Node.js + Express + MongoDB).
Hard Rules
- JSX only — no TypeScript, no .ts/.tsx files, no type annotations
- ES modules —
import/exporteverywhere, neverrequire - Tailwind CSS — no other styling approaches
- Use
@/path alias for all client-side imports (maps toclient/src/) - React Query for data fetching, react-hook-form + zod for forms
- Shadcn UI components from
@/components/ui/— don't create new CSS - Backend: routes -> controllers -> models pattern, all under
/api/ - Auth: JWT tokens,
authmiddleware +roleGuard(...)for protected routes - Roles: president, pm, mc, domain_leader, member
Code Patterns
Frontend Component
import { useAuth } from "@/hooks/useAuth";
import { Button } from "@/components/ui/button";
import { toast } from "sonner";
export default function MyComponent() {
// component logic
}
Backend Route + Controller
// routes/feature.js
import { Router } from "express";
import { getAll } from "../controllers/featureController.js";
import auth from "../middleware/auth.js";
const router = Router();
router.get("/", auth, getAll);
export default router;
// controllers/featureController.js
import Model from "../models/Model.js";
export const getAll = async (req, res) => {
try {
const items = await Model.find();
res.json(items);
} catch (error) {
res.status(500).json({ message: error.message });
}
};
React Query Hook
import { useQuery, useMutation, useQueryClient } from "@tanstack/react-query";
import api from "@/api/axios";
export function useItems() {
return useQuery({
queryKey: ["items"],
queryFn: async () => { const { data } = await api.get("/items"); return data; },
});
}
Existing Modules
Events, Decisions, Strikes, Candidates, Members — each has model, controller, routes, hook, components, and page already built. Follow the same patterns when extending.
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 · 73 lines · 530 tokens per session scan A 6ae1b374650a
PCIC copilot-instructions.md is an instructions file published in the GitHub repository ayimmam/PCIC (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 530 tokens to every session, about $0.0027 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.