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/code-conventions)<a href="https://agentmods.dev/rules/vypdev/copilot/code-conventions"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/code-conventions/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/code-conventions"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/code-conventions.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.00000 | $0.00203 |
| Opus 5.5 | $0.00000 | $0.00081 |
| Sonnet 5.5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
code-conventions 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
Code conventions
The maintained convention document is _agent/docs/code-conventions.md.
- Application code uses semantic ports and application logging; it must not import runtime loggers, concrete repositories, Octokit, or provider DTOs.
- Input names come from
src/application/contracts/input_keys.ts. - Single-action names come from
src/data/model/action_types.ts. - Add a new input through
action.yml, the input contract, its runtime adapters, tests, setup workflows when applicable, and public documentation. - Prefer focused policies and ports over aggregate facades or delegating wrappers.
- Keep code compatible with
@vercel/ncc; regeneratebuild/withpnpm buildand never edit generated files directly. - Run
pnpm lint,pnpm typecheck, and the proportionate Jest suites before committing.
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 · -12 lines 6b73cb83f8a1
- 1mo ago First seen · 35 lines · 0 tokens per session scan A 678dce985134
code-conventions is a cursor rule published in the GitHub repository vypdev/copilot (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 203 tokens. 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
code-review-en
Code Review Guidelines (English).
task-summary
Enforce Summary and Session Log blocks on every coding response when session tracking is enabled.
api-steps
How to create HTTP endpoints in Motia.
virtual-steps
Connecting nodes virtually and creating a smooth flow in Workbench.
201-bugbot-autofix
200: Responding to BugBot PR comments.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.