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.
git clone --depth 1 https://github.com/vypdev/copilotWrote 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/rules/vypdev/copilot/project-context)<a href="https://agentmods.dev/rules/vypdev/copilot/project-context"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/project-context/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/rules/vypdev/copilot/project-context"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/project-context.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.00279 | $0.00279 |
| Opus 5.5 | $0.00112 | $0.00112 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
project-context 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.
What it actually says
Copilot project context
Copilot is a GitHub Action and CLI for issue/PR automation, branch management, Bugbot, and configurable release/hotfix orchestration. Agent roles can use Codex, OpenCode, or Cursor according to the validated repository configuration; no provider is an implicit compatibility path for another.
Use Node 24 or newer and pnpm from the repository root:
nvm use 24
pnpm install
pnpm build
pnpm test
pnpm test:coverage
pnpm lint
pnpm typecheck
Important boundaries:
- Runtime inputs:
action.ymlandsrc/application/contracts/input_keys.ts. - Single actions:
src/data/model/action_types.ts. - Architecture:
_agent/docs/architecture.md,docs/development/architecture.mdx, anddocs/dependency-rules.md. - Flows:
_agent/docs/usecase-flows.md. - Coding rules:
_agent/docs/code-conventions.md. - Generated bundles:
build/; regenerate them withpnpm build, never edit them directly.
When a contract changes, update source, tests, setup workflows, action.yml,
public documentation, internal agent documentation, and generated bundles in
the same change.
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 Changed · -2 lines · -190 tokens per session 9abda42dc4df
- 1mo ago First seen · 41 lines · 469 tokens per session scan A e0e721a08d9f
project-context is a cursor rule published in the GitHub repository vypdev/copilot (3 stars, last pushed today), licensed MIT. It adds 279 tokens to every session, about $0.0011 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 cursor rules, from other repositories
changesets
Changeset format and bump rules enforced by CI.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
git_rules
When asked to interact with git, github or project management tooling (jira, linear, asana etc).
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.