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/putervision/spc/copilot-instructionsgit clone --depth 1 https://github.com/putervision/spcWhat 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.01755 | $0.01755 |
| Opus 5 | $0.00877 | $0.00877 |
| Sonnet 5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00176 | $0.00176 |
Grade B, and why
spc copilot-instructions.md scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
* **Google Antigravity (`~/.gemini/config/config.json`)**: Add these rules to your `"globalPermissionGrants"` -> `"allow"` list: This is a copy
94% identical to state-memory-mcp copilot-instructions.md — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Memory (state-memory-mcp)
This project tracks workflow state, tasks, design decisions, and blockers using state-memory-mcp with project slug "spc".
1. Priority Order
Before doing any coding or investigation:
manage_sessions(action: "start")— Start a tracking session for full change attribution.get_analytics(action: "summary")— Run to understand current project state, active branches, and overall progress.manage_tasks(action: "next")— Query prioritized runnable tasks.manage_tasks(action: "find_blockers")— Identify any active blockers preventing progress.manage_nodes(action: "list")— Find pending tasks, past decisions, or milestones.query_graph(action: "trace")— Trace what depends on or blocks a task.
2. When to Write to the Graph
You MUST update the graph as you work:
- Starting a session: Always call
manage_sessions(action: "start", agent_id: "my-agent")to track all mutations under a unique session. - Starting a new task: Create a node with
manage_nodes(action: "create", type: "task", title: "...", session_id: session_id). - Making a design or implementation decision: Document it with
manage_nodes(action: "create", type: "decision", title: "...", metadata: { "rationale": "..." }, session_id: session_id). - Encountering a blocker: Record the blocker with
manage_nodes(action: "create", type: "blocker", title: "...", session_id: session_id)and connect it usingmanage_edges(action: "add", type: "blocks", source_id: blocker_id, target_id: task_id, session_id: session_id). - Adding observation notes: Atomically log notes using
manage_nodes(action: "add_note", text: "...", attach_to: node_id). - Batch updates: Bulk update tasks/nodes using
manage_nodes(action: "batch_update", ids: ["..."], status: "done"). - Completing a task: Update status to done using
manage_tasks(action: "complete", task_id: task_id)ormanage_nodes(action: "update", id: task_id, status: "done"). - Creating/generating a new file: Create an artifact node with
manage_nodes(action: "create", type: "artifact", title: "...", session_id: session_id)and connect it usingmanage_edges(action: "add", type: "produces", source_id: task_id, target_id: artifact_id).
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 · 77 lines · 1,755 tokens per session scan B 94614c966b2c
spc copilot-instructions.md is an instructions file published in the GitHub repository putervision/spc (39 stars, last pushed 11d ago), licensed MIT. It adds 1,755 tokens to every session, about $0.0088 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 94% identical to state-memory-mcp copilot-instructions.md, differing in 12 lines, and is treated as a copy.
Other instructions, from other repositories
static-analysis AGENTS.md
Instructions for analysis-tools-dev/static-analysis, covering guidelines for ai agents and assistants and 🤖 instructions for the ai.
CodeBoarding AGENTS.md
Instructions for CodeBoarding/CodeBoarding, covering system-wide recommendations for agent execution, 1. environment and virtual environment setup, 2. dependency and repository navigation, 3. code quality and testing standards and 4. execution flow and tool patterns.
OpenLore CLAUDE.md
Instructions for clay-good/OpenLore, covering openlore mcp tools — when to use them, agent skills, issue tracker, triage labels and domain docs.
semgrep CLAUDE.md
Claude Code instructions for semgrep/semgrep, a project described as: Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
PhpCodeArcheology CLAUDE.md
Instructions for PhpCodeArcheology/PhpCodeArcheology, covering claude.md — phpcodearcheology, project overview, language, tech stack and project structure.
omen CLAUDE.md
Instructions for panbanda/omen, covering claude.md, build and development commands, setup git hooks (run once after clone), format code and run linter.