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/adobe/spacecat-api-service/copilot-instructionsgit clone --depth 1 https://github.com/adobe/spacecat-api-serviceWhat 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.01644 | $0.01644 |
| Opus 5 | $0.00822 | $0.00822 |
| Sonnet 5 | $0.00329 | $0.00329 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
spacecat-api-service 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot PR Review Instructions
1. Review Goals and Priorities
Your primary purpose is to identify behavior-breaking defects, security/auth gaps, and missing tests for changed behavior. When such issues are present, prioritize them above all other considerations (performance, cost, style).
Use three severities:
- Critical – Bugs, regressions, security issues, missing required validation, or missing tests for changed behavior. Respond with: “This PR should not be merged until this is fixed.”
- Major – Missing documentation, missing but non-blocking tests, realistic performance or cost concerns.
- Minor – Stylistic suggestions or optional improvements. Only list Minor issues if no Critical issues exist.
If you find any Critical issue, list it first and deprioritize all other feedback.
2. Output Format (Always Required)
Respond using the following structure:
Summary
1–3 sentences describing the overall health of the PR.
Issues
Critical
- List each issue, quoting relevant code and suggesting a concrete fix.
Major
- As above.
Minor
- As above. Only include if there are no Critical issues.
Suggested Tests
- Describe which tests should be added or updated (if applicable). If no test changes are needed, state that clearly.
3. Core Checks (Apply to Every PR)
3.1 Bug & Regression Scan
Look for defects including:
- Missing or incorrect null/undefined checks.
- Incorrect async/await handling.
- Miswired routes or controller mismatches.
- Incorrect DTO usage or leaking internal models.
- Logic changes without corresponding test updates.
If you see changed behavior without new or updated tests, mark as Critical.
3.2 Security & Authorization
For any controller returning tenant-specific data:
If:
- The controller does not instantiate
AccessControlUtil.fromContext(ctx), or - It does not call
hasAdminAccess()orhasAccess(entity, subService, productCode),
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 · 273 lines · 1,644 tokens per session scan A 8e789b6cd3d6
spacecat-api-service copilot-instructions.md is an instructions file published in the GitHub repository adobe/spacecat-api-service (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,644 tokens to every session, about $0.0082 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.