SidewalkWebpage: Instructions file for GitHub Copilot

.github/instructions/evolutions.instructions.md

SidewalkWebpage evolutions.instructions.md is an instructions file for GitHub Copilot from ProjectSidewalk/SidewalkWebpage. It costs 440 tokens per session, scanned A, original, MIT.

A set of project-specific instructions for reviewing database schema changes in Project Sidewalk. A schema describes tables, columns, relationships, and rules in a database.

In plain words
What is it for?
Use it to review evolution files in pull requests, including new or changed tables, foreign keys, uniqueness rules, bounded values, and renamed database objects.
Why use it?
It helps catch missing database ownership, constraints, validation rules, and rename cleanup before schema changes are accepted. It also checks that database rules match the application's data model.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is ProjectSidewalk/SidewalkWebpage's own configuration. It tells GitHub Copilot how to work on SidewalkWebpage itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SidewalkWebpage configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProjectSidewalk/SidewalkWebpage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProjectSidewalk/SidewalkWebpage/develop/.github/instructions/evolutions.instructions.md
Clone the repo
git clone --depth 1 https://github.com/ProjectSidewalk/SidewalkWebpage

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for SidewalkWebpage evolutions.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/projectsidewalk/sidewalkwebpage/evolutions/github.svg)](https://agentmods.dev/instructions/projectsidewalk/sidewalkwebpage/evolutions)
Your own site
<a href="https://agentmods.dev/instructions/projectsidewalk/sidewalkwebpage/evolutions"><img src="https://agentmods.dev/badge/instructions/projectsidewalk/sidewalkwebpage/evolutions/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.

agentmods 80×15 button for SidewalkWebpage evolutions.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/projectsidewalk/sidewalkwebpage/evolutions"><img src="https://agentmods.dev/badge/instructions/projectsidewalk/sidewalkwebpage/evolutions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 440 This file is loaded in full into every session.
When invoked 440 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00440 $0.00440
Opus 5.5 $0.00176 $0.00176
Sonnet 5.5 $0.00088 $0.00088
Haiku 4.5 $0.00044 $0.00044

Measured 2mo ago against content hash b0576f7d7506, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

SidewalkWebpage evolutions.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 2mo 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.

.github/instructions/evolutions.instructions.md · 28 lines

What it actually says

Play evolution (schema) review — highest-value checks

  • One evolution file per PR. Flag a PR minting a new-numbered file when its changes could fold into the PR's existing evolution.
  • Owner: every CREATE TABLE must be followed by ALTER TABLE <name> OWNER TO sidewalk; in the same file. Flag any missing it. Tables ONLY — not enum types, views, or standalone sequences; SERIAL/identity sequences are covered automatically by the table's owner change.
  • Full constraints — don't lean on the app. For each new/altered table flag missing: NOT NULL on never-null columns, UNIQUE/PK on natural keys & 1:1 relationships, a FOREIGN KEY for every reference, a CHECK for bounded domains (severity 1–3, non-negative counts, 0–1 fractions, valid lat/lng). Each must be mirrored in the Slick model.
  • Closed value sets: prefer a Postgres enum type (high-row / runtime-written / Scala-mirrored columns) or a CHECK (col IN (...)) (tiny config tables) over a lookup table or bare text. When an enum replaces a same-named lookup table, DROP TABLE must precede CREATE TYPE.
  • Renames leave fossils. An evolution renaming a table/column must also ALTER TABLE ... RENAME CONSTRAINT / ALTER INDEX ... RENAME every constraint and index embedding the old name (to <table>_<column>_{fkey,key,pkey,check}) and update the Slick name string. Flag a rename that omits this.
  • Parser trap: no ; inside a -- comment — Play's evolution parser splits statements on ; and will break. Flag it.
  • Both # --- !Ups and # --- !Downs sections must be present.
Changes

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.

  1. 2mo ago First seen · 28 lines · 440 tokens per session scan A b0576f7d7506

Subscribe to this mod's changes

SidewalkWebpage evolutions.instructions.md is an instructions file published in the GitHub repository ProjectSidewalk/SidewalkWebpage (111 stars, last pushed today), licensed MIT. It adds 440 tokens to every session, about $0.0018 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-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens