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/leei1337/phantom-neural-cortex/copilot-instructionsgit clone --depth 1 https://github.com/LEEI1337/phantom-neural-cortexWrote 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/leei1337/phantom-neural-cortex/copilot-instructions)<a href="https://agentmods.dev/instructions/leei1337/phantom-neural-cortex/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/leei1337/phantom-neural-cortex/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 | $0.00991 | $0.00991 |
| Opus 5 | $0.00495 | $0.00495 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
phantom-neural-cortex 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 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Custom Instructions
Project Context
This is a Claude Code configuration repository optimized for professional development.
Code Style & Standards
TypeScript/JavaScript
- Use TypeScript with strict mode enabled
- Prefer functional components with hooks (React)
- Use async/await over promises
- Explicit return types for functions
- No
anytypes - useunknownif necessary
Python
- Follow PEP 8 style guide
- Type hints for all function signatures
- Use dataclasses or Pydantic models
- Async/await for I/O operations
General
- Maximum line length: 100 characters
- Use meaningful variable names
- Single responsibility principle
- Comment complex logic only
- No dead code or commented-out code
Security Requirements
- Never hardcode secrets, API keys, or passwords
- Always validate and sanitize user inputs
- Use parameterized queries (prevent SQL injection)
- Implement proper authentication/authorization
- Follow OWASP Top 10 guidelines
- Use HTTPS only for production APIs
Testing Requirements
- Minimum 80% code coverage for critical paths
- Unit tests for all public functions
- Integration tests for API endpoints
- E2E tests for critical user flows
- Test edge cases and error conditions
Documentation
- JSDoc/PyDoc for all public APIs
- README for each module/package
- Inline comments for complex algorithms
- ADRs (Architecture Decision Records) for major changes
Performance Guidelines
- Optimize database queries (use EXPLAIN)
- Lazy load components where possible
- Minimize bundle size (code splitting)
- Use memoization for expensive computations
- Monitor and optimize rendering performance
Error Handling
- Use try/catch for all async operations
- Provide meaningful error messages
- Log errors with context
- Never silently catch errors
- Implement proper error boundaries (React)
Git Commit Messages
Format: <type>(<scope>): <subject>
Types:
- feat: New feature
- fix: Bug fix
- docs: Documentation
- style: Formatting
- refactor: Code restructuring
- test: Adding tests
- chore: Maintenance
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 · 158 lines · 991 tokens per session scan A 3a520737126f
phantom-neural-cortex copilot-instructions.md is an instructions file published in the GitHub repository LEEI1337/phantom-neural-cortex (5 stars, last pushed 6mo ago), licensed MIT. It adds 991 tokens to every session, about $0.0050 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
android-tools-mcp CLAUDE.md
Instructions for amsavarthan/android-tools-mcp, covering android-tools-mcp, build, run / test, connect with claude code and architecture.
LogseqBrain CLAUDE.md
Instructions for jame581/LogseqBrain, covering claude.md, what this repo is, architecture, shared references (since v0.6.0) and graph path resolution (every skill does this).
ClawRouter CLAUDE.md
Claude Code instructions for BlockRunAI/ClawRouter, covering clawrouter, commands, project structure, key dependencies and conventions.
SearChat CLAUDE.md
Claude Code instructions for yokingma/SearChat, covering claude.md, project overview, architecture, monorepo structure and key technologies.
apm python.instructions.md
Python development guidelines.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.