agentregistry copilot-instructions.md

Instructions for GitHub Copilot work in the AgentRegistry repository, including the requirement to follow repository guidance and keep pull-request descriptions current. A pull request is a proposed code change submitted for review.

In plain words
What is it for?
Reviewing pull-request templates, creating pull requests, updating existing descriptions with progress reports, and documenting changes under the required headings.
Why use it?
They prevent agents from using the wrong tool or format when creating or updating a pull request, which could cause automated checks to fail.

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/agentregistry-dev/agentregistry/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/agentregistry-dev/agentregistry

Made for: GitHub Copilot.

Per session 290 This file is loaded in full into every session.
When invoked 290 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.00290 $0.00290
Opus 5 $0.00145 $0.00145
Sonnet 5 $0.00058 $0.00058
Haiku 4.5 $0.00029 $0.00029

Measured 2d ago against content hash b724f17c016a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agentregistry 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 · 18 lines

What it actually says

GitHub Copilot Instructions

Read and follow AGENTS.md for repo-local coding and workflow guidance.

Before creating or updating a pull request, review the PR authoring rules in AGENTS.md and follow .github/PULL_REQUEST_TEMPLATE.md.

Keeping the PR Description Up-to-Date

The report_progress tool is the only way to update an existing PR's description. The create_pull_request tool only works when no PR exists yet — it cannot edit the body of an existing PR.

Whenever you make meaningful progress on a task:

  1. Call report_progress with an accurate prDescription that follows .github/PULL_REQUEST_TEMPLATE.md.
  2. Use the exact top-level headings from the template: # Description, # Change Type, # Changelog. The CI labeler enforces a # Description section (single #) and will fail if ## headings are used or the section is missing.
  3. Populate every required section of the template (Description, Change Type, Changelog).
  4. Do not consider the task complete until the PR description has been updated via report_progress.

Important: The prDescription you pass to report_progress becomes the literal GitHub PR body. Always start it with # Description (not ## Description) so the CI labeler can find the required section.

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 · 18 lines · 290 tokens per session scan A b724f17c016a

Subscribe to this mod's changes

agentregistry copilot-instructions.md is an instructions file published in the GitHub repository agentregistry-dev/agentregistry (478 stars, last pushed 4d ago), licensed Apache-2.0. It adds 290 tokens to every session, about $0.0014 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.