ASSERT: Instructions file for GitHub Copilot

.github/copilot-instructions.md

ASSERT copilot-instructions.md is an instructions file for GitHub Copilot from responsibleai/ASSERT. It costs 478 tokens per session, scanned A, original, MIT.

Instructions for GitHub Copilot, an AI coding assistant, in the ASSERT repository, pointing it to the repository’s main guidance and user-facing workflows.

In plain words
What is it for?
Use them when Copilot runs the ASSERT evaluation workflow or when maintaining its prompt files and repository-specific guidance.
Why use it?
They keep Copilot’s instructions from drifting from the main project rules and prevent it from exposing private environment values.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: reads .claude/ paths; mentions Claude Code; mentions AGENTS.md.

This is responsibleai/ASSERT's own configuration. It tells GitHub Copilot how to work on ASSERT 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 ASSERT configures →

Reuse

Borrowing it

Nothing to install: this file belongs to responsibleai/ASSERT. 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/responsibleai/ASSERT/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/responsibleai/ASSERT

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 ASSERT copilot-instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/responsibleai/assert/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/responsibleai/assert/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 478 This file is loaded in full into every session.
When invoked 478 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.00478 $0.00478
Opus 5.5 $0.00191 $0.00191
Sonnet 5.5 $0.00096 $0.00096
Haiku 4.5 $0.00048 $0.00048

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

Security

Grade A, and why

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

.github/copilot-instructions.md · 17 lines

How it starts

The opening of the file, as written. The whole thing — 17 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Copilot instructions

Read ../AGENTS.md first. It is the single source of truth for this repository's orientation, terminology, target selection, and setup commands. This file is intentionally a thin pointer — do not copy AGENTS.md content here, so the two cannot drift.

Never read, print, commit, or infer secrets from .env or other local environment files.

User-facing skills

Use the matching prompt file when the user's request matches:

  • run-assert-eval (.github/prompts/run-assert-eval.prompt.md): Run an end-to-end ASSERT evaluation against a described risk. Risks come from Clarity (recommended — drives the Clarity MCP tools (run_clarity) in-IDE to surface failure modes the user hasn't considered) or directly from the user as prose, a PRD, design doc, threat model, or red-team finding; Clarity is never required. Then follows workflows/measure-clarity-failures.md — human triage, splits the selected risks into one atomic config per behavior, runs the pipeline, and summarizes scored results with cited failures. Config generation is owned by workflows/research-eval-dimensions.md, which runs downstream of both risk sources: given an already-named risk, it reviews how that risk has been evaluated in the literature and converts the findings into the test-set design — every behavior category, stratify dimension, and judge dimension is researched against retrieved primary sources under a ≥2-independent-source gate, N complete generation passes are run and semantically deduplicated, the dimension set is blocked on explicit user approval, and the result is written as a cited examples/<domain>/<risk>/eval_config.yaml. Reports policy_violation and overrefusal separately. To fix and prove a failure, workflows/govern-and-remeasure.md generates an ACS policy from the findings (assert-ai acs generate) and re-runs the same eval against the governed agent to measure the failure-rate delta.

Equivalent guidance for other assistants lives in .claude/skills/run-assert-eval/SKILL.md (Claude Code) and .cursor/rules/assert.mdc (Cursor). Keep all three aligned when you change the methodology.

Read the full file on GitHub · 17 lines

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. 1mo ago Changed · +128 tokens per session 8301e8347608
  2. 1mo ago First seen · 17 lines · 350 tokens per session scan A 759889dd38b8

Subscribe to this mod's changes

ASSERT copilot-instructions.md is an instructions file published in the GitHub repository responsibleai/ASSERT (352 stars, last pushed 4d ago), licensed MIT. It adds 478 tokens to every session, about $0.0019 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