ASSERT copilot-instructions.md

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

Install

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.

agentmods
npx agentmods add instructions/responsibleai/assert/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/responsibleai/ASSERT

Made for: GitHub Copilot.

Per session 350 This file is loaded in full into every session.
When invoked 350 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00350 $0.00350
Opus 5 $0.00175 $0.00175
Sonnet 5 $0.00070 $0.00070
Haiku 4.5 $0.00035 $0.00035

Measured 2d ago against content hash 759889dd38b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

.github/copilot-instructions.md · 17 lines

What it actually says

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, or threat model; 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. 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.

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. 2d 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 (233 stars, last pushed 3d ago), licensed MIT. It adds 350 tokens to every session, about $0.0018 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.

Related

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,040 tokens

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.

langchain-ai/langchain · 4,345 tokens