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/themeparks/parksapi/copilot-instructionsgit clone --depth 1 https://github.com/ThemeParks/parksapiWhat 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.02418 | $0.02418 |
| Opus 5 | $0.01209 | $0.01209 |
| Sonnet 5 | $0.00484 | $0.00484 |
| Haiku 4.5 | $0.00242 | $0.00242 |
Grade A, and why
parksapi 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot review instructions for parksapi
These instructions describe project-specific conventions. Do not flag the patterns below as defects — they are intentional. Use this file to calibrate review feedback before commenting.
Authoritative source for conventions:
CLAUDE.md. This file is a Copilot-focused condensation; if there is a conflict,CLAUDE.mdwins.
Project overview
parksapi is a TypeScript ESM library that fetches real-time theme park data (wait times, schedules, entities) from 75+ park implementations. All park integrations live under src/parks/<park>/. The core abstraction is the Destination base class with a Template Method pattern: subclasses implement _init(), buildEntityList(), buildLiveData(), buildSchedules(), plus override getDestinations() to declare the resort. The other public get*() methods (getEntities, getLiveData, getSchedules) must not be overridden.
Node 24+, npm 11+, ES2022 modules, decorators enabled.
Decorator-based design
Five decorators carry most of the framework:
| Decorator | Purpose |
|---|---|
@destinationController({category}) |
Auto-registers the destination and applies @config to the class. Never apply @config to a class directly when using this decorator. |
@config |
Property-level config injection. Values resolve from instance config → {CLASSNAME}_{PROP} env var → {PREFIX}_{PROP} env var → property default. |
@cache({ttlSeconds, key?, callback?, cacheVersion?}) |
SQLite-backed memoisation with TTL. |
@http({cacheSeconds?, retries?, ...}) |
Queue-based HTTP request wrapper. |
@inject({eventName, hostname?, tags?, priority?}) |
Sift.js (MongoDB-like) event filter for cross-cutting concerns (auth, headers, error handling). |
Patterns the project uses (do not flag these)
1. Empty-string config defaults are intentional
@config apiBase: string = '';
@config token: string = '';
@config email: string = '';
CLAUDE.md requires that no URLs, keys, tokens, or credentials ever appear hardcoded in source. Empty-string defaults force configuration via .env and are the documented convention. Do not suggest providing fallback URLs, default keys, or upfront validation that throws on empty strings. The HTTP layer's URL-construction error is the documented failure signal when env vars are missing.
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 · 184 lines · 2,418 tokens per session scan A 165eaf631161
parksapi copilot-instructions.md is an instructions file published in the GitHub repository ThemeParks/parksapi (140 stars, last pushed 3d ago), licensed MIT. It adds 2,418 tokens to every session, about $0.0121 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-30.
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.