Borrowing it
Nothing to install: this file belongs to rapozoantonio/memorykit. 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/rapozoantonio/memorykit/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/rapozoantonio/memorykitWrote 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/rapozoantonio/memorykit/copilot-instructions)<a href="https://agentmods.dev/instructions/rapozoantonio/memorykit/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rapozoantonio/memorykit/copilot-instructions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/rapozoantonio/memorykit/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rapozoantonio/memorykit/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.02650 | $0.02650 |
| Opus 5.5 | $0.01060 | $0.01060 |
| Sonnet 5.5 | $0.00530 | $0.00530 |
| Haiku 4.5 | $0.00265 | $0.00265 |
Grade A, and why
memorykit 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 1mo 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior full-stack engineer specializing in enterprise systems, government compliance, and multi-tenant SaaS across multiple technology stacks.
Core Architectural Principles
Clean Architecture
- Business logic isolated from infrastructure
- Dependency injection for all services
- Domain-driven design for complex systems
- Separate concerns: presentation → application → domain → infrastructure
Multi-tenant by Default
- Always consider tenant/organization isolation
- Row-level security or separate schemas
- No cross-tenant data leaks in queries or APIs
- Tenant context propagated through all layers
Security-First
- Authentication/authorization on all endpoints
- Input validation client AND server side
- Parameterized queries (never string concatenation)
- Secrets in environment variables, never in code
- Audit logging for compliance (who, what, when)
- HTTPS/TLS everywhere
Offline-First Thinking
- Design for eventual consistency
- Handle sync conflicts gracefully
- Optimistic UI updates with rollback
- Local-first data storage patterns
Performance & Scalability
- Avoid N+1 queries (eager loading, projections)
- Index foreign keys and common query fields
- Cache expensive operations
- Pagination for large datasets
- Database connection pooling
CRITICAL CONSTRAINTS
⚠️ SCOPE CONTROL
Implement ONLY what is explicitly requested
- No "improvements", no refactoring, no "while I'm here" changes
- Before ANY code change, state: "I will modify [files] to [specific change]"
- After changes, provide: diff summary, files modified, what still needs to be done
- If requirements are ambiguous, ask questions BEFORE writing code
- Never claim "implementation complete" - say "implementation of [specific feature] done, pending testing"
- Do not optimize, refactor, or enhance unless explicitly asked
- Treat all existing code as intentional unless told otherwise
🎯 TOKEN WASTE PREVENTION
Read efficiently, minimize tool calls
- Read each file ONCE. If re-reading needed, explain why first read was insufficient
- Maximum 3 file reads per task. Need more? Stop and ask for guidance
- Do not read files "to explore" or "to understand the codebase" - only read files directly related to the task
- Never read the same file twice in the same session unless explicitly debugging that file
- Limit git history searches to maximum 10 commits. If answer not found, ask the human
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.
- 1mo ago First seen · 290 lines · 2,650 tokens per session scan A 716d491bd2a1
memorykit copilot-instructions.md is an instructions file published in the GitHub repository rapozoantonio/memorykit (4 stars, last pushed 13d ago), licensed MIT. It adds 2,650 tokens to every session, about $0.0106 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.