Borrowing it
Nothing to install: this file belongs to ai-ecoverse/slicc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ai-ecoverse/slicc/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/ai-ecoverse/sliccWrote 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/instructions/ai-ecoverse/slicc/copilot-instructions)<a href="https://agentmods.dev/instructions/ai-ecoverse/slicc/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ai-ecoverse/slicc/copilot-instructions.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.1 | $0.00971 | $0.00971 |
| Opus 5 | $0.00485 | $0.00485 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
slicc 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 yesterday.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLICC — Copilot Code Review Instructions
Review SLICC's five runtimes (webapp, extension, Node, Swift, iOS) against these blind
spots. Flag only genuine risks. Catalog: docs/review-patterns.md.
1. Error-path coverage (often Critical)
External calls need bounded failure: timeouts, retry/backoff, surfaced errors. Flag unbounded fetch(), E2B calls, async work.
2. Cross-runtime parity (often Critical)
Shared behavior needs peer updates or explicit exclusion. Check Node ↔ Swift (endpoints,
signing, DA origin allow-list / aem:// #2811), browser ↔ extension (mounts, VFS, secrets).
3. UI state preservation
DOM rebuilds (innerHTML, replaceChildren, reflow) must capture and restore live state.
4. CDP / Chrome edge cases
Foreground the page (Page.bringToFront() / wake renderer) before screenshots or capture.
Validate CDP target + port before trusting them; handle disconnects.
5. Native / macOS permissions
Native protected-resource access needs entitlements/usage descriptions, TCC checks,
graceful denial. A File Provider appex must embed+sign every @rpath framework it
links (host Resources/ is invisible) and declare its transport's network entitlements.
No keychain-access-groups on the macOS File Provider: that restricted entitlement needs
an appex-specific Developer ID profile, else AMFI refuses launch (extensionKit error 2).
6. Model metadata / provider pipeline
When model IDs or provider metadata change, verify reasoning, input, cost, thinking levels through discovery, enrichment, account storage, API effort mapping.
7. Test coverage
New src/ files need mirrored tests; changed logic updated tests; bug fixes a
regression test. Don't lower coverage floors.
8. Follower surface wiring parity (often Critical)
Leader broadcasts need follower handlers and UI actions. Check live, follower, and extension boot paths; preserve shared fallbacks; prefer capability checks to float names.
9. Origin / bridge routing contract (often Major)
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.
- yesterday First seen · 90 lines · 971 tokens per session scan A 4bcf93f33ad3
slicc copilot-instructions.md is an instructions file published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 971 tokens to every session, about $0.0049 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-09-05.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.