agentmods.dev

skill-recorder copilot-instructions.md

Repository instructions are written rules for coding agents working on a software project. They say ongoing work and pull requests should use the current release branch, such as release/0.3.0, instead of the main branch.

In plain words
What is it for?
Use them when creating branches, opening pull requests, or checking which branch should receive new work in microsoft/skill-recorder.
Why use it?
They prevent changes from being based on an outdated branch or merged into the wrong place. This keeps development aligned with the version currently being prepared.

Instructions file for GitHub Copilot

3.7k +36 9d ago A scan 280 tokens original MIT
View the source file microsoft/skill-recorder
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/microsoft/skill-recorder/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/microsoft/skill-recorder

Made for: GitHub Copilot.

Per session 280 This file is loaded in full into every session.
When invoked 280 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.00280 $0.00280
Opus 5 $0.00140 $0.00140
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

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

Security

Grade A, and why

skill-recorder 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 · 32 lines

What it actually says

Repository instructions for coding agents

Pull requests target the active release branch, not main

Ongoing work in this repository lands on the current release branch, not main. Release branches are named release/<semver> — currently release/0.3.0, the highest-versioned release/* branch on origin. main trails the release branch and only advances when a version is cut and merged (see RELEASING.md).

Unless a task explicitly says otherwise:

  • Base new work on the current release branch, not main:

    git fetch origin
git switch -c <your-branch> origin/release/0.3.0

  • Open pull requests with the current release branch as the base, not main:

    gh pr create --repo microsoft/skill-recorder --base release/0.3.0 --head <your-branch>

  • Find the current release branch (pick the highest semver) with:

    git ls-remote --heads origin 'release/*'

Target main only for the release merge described in RELEASING.md.

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 · 32 lines · 280 tokens per session scan A 73a54fb9a8d4

Subscribe to this mod's changes

skill-recorder copilot-instructions.md is an instructions file published in the GitHub repository microsoft/skill-recorder (3,731 stars, last pushed 9d ago), licensed MIT. It adds 280 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.

agent-skillsai-agentsautomationcopilotcopilot-clicopilot-cowork
Related

Other instructions, from other repositories

copilotd copilot-instructions.md

Instructions for DamianEdwards/copilotd, covering copilot instructions for copilotd, build & run, build, run from source (auto-builds and passes all args through) and architecture.

DamianEdwards/copilotd · 1,292 tokens

ai-ready AGENTS.md

Instructions for johnpapa/ai-ready, covering ai-ready repo — agent guide, repository structure, tech stack, build & run and testing.

johnpapa/ai-ready · 1,143 tokens

ai-ready copilot-instructions.md

Instructions for johnpapa/ai-ready, covering copilot instructions — ai-ready, project type, writing conventions, markdown and yaml (skill frontmatter, workflows, issue templates).

johnpapa/ai-ready · 516 tokens

DPlex copilot-instructions.md

Instructions for Ron537/DPlex, covering dplex — copilot instructions, build & run, architecture, process boundaries and provider system (ai tool abstraction).

Ron537/DPlex · 2,614 tokens

spec-kit-copilot AGENTS.md

Instructions for github/spec-kit-copilot, covering what this repository is, core skills plugin, core decisions (do not silently undo) and when revving the core skills plugin.

github/spec-kit-copilot · 2,177 tokens

oh-my-copilot AGENTS.md

Instructions for RobinNorberg/oh-my-copilot, covering oh-my-copilot - intelligent multi-agent orchestration and setup.

RobinNorberg/oh-my-copilot · 5,150 tokens