What is copilot-tooling AGENTS.md?

A set of project instructions for agents working on the grehnen/copilot-tooling repository. It defines principles, coding preferences, required skills, and GitHub issue-tracking conventions.

Use it when contributing to that repository, especially for code changes, issue triage, and tasks that need its defined agent behaviour.

It gives agents project-specific rules for making decisions, asking questions, writing code, and handling issues. This keeps their work aligned with the repository's expectations.

copilot-tooling AGENTS.md — Instructions file by grehnen

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/grehnen/copilot-tooling/agents-md

Clone the repo

git clone --depth 1 https://github.com/grehnen/copilot-tooling

Made for: Codex, OpenCode.

Per session 634 This file is loaded in full into every session.

When invoked 634 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.

Model	Per session	Once invoked
Fable 5	$0.00634	$0.00634
Opus 5	$0.00317	$0.00317
Sonnet 5	$0.00127	$0.00127
Haiku 4.5	$0.00063	$0.00063

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

Security

Grade A, and why

copilot-tooling AGENTS.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.

AGENTS.md · 73 lines

How it starts

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

{{PROJECT_NAME}} — Project Guidelines

{{One-sentence description of what the project does, who uses it, and how.}}

Overall Principles (Very Important)

ALWAYS prefer asking the user for input and clarification over making assumptions.
ALWAYS use the question-tool (vscode/askQuestions) when asking the user questions, and always provide your recommended answer.
ALWAYS select the appropriate skill for a specific task.
Be EXTREMELY brief in your responses. Sacrificse grammar for brevity.

Code Style

Avoid writing duplicated code and instead create reusable functions and utility components. Try to reuse existing code whenever possible.
Prefer separating the code into smaller, focused files.
Use descriptive variable and function names. Use comments only when necessary, such as when explaining complex logic or decisions.
The project is in early development, so breaking changes are completely fine.

Agent skills

Issue tracker

Issues for this repo are tracked in GitHub Issues. See docs/agents/issue-tracker.md.

Triage labels

This repo uses the canonical triage labels: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. See docs/agents/triage-labels.md.

Domain docs

This repo uses a single-context domain-doc layout. See docs/agents/domain.md.

Tech Stack

Structure

Read the full file on GitHub · 73 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.

2d ago First seen · 73 lines · 634 tokens per session scan A af187b18aceb

Subscribe to this mod's changes

copilot-tooling AGENTS.md is an instructions file published in the GitHub repository grehnen/copilot-tooling (2 stars, last pushed 1mo ago), licensed MIT. It adds 634 tokens to every session, about $0.0032 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-31.

Project management

planning-with-files AGENTS.md

AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.

OthmanAdi/planning-with-files · 2,236 tokens

DevoxxGenieIDEAPlugin GEMINI.md

Instructions for devoxx/DevoxxGenieIDEAPlugin, a project described as: DevoxxGenie is an agentic plugin for IntelliJ IDEA that uses local LLM's (Ollama, LMStudio, GPT4All, Jan and Llama.cpp) and Cloud based LLMs to help review, test, explain your project code. Latest version now also supports Spec Driven Development…

devoxx/DevoxxGenieIDEAPlugin · 257 tokens

autoharness AGENTS.md

Instructions for tigerless-labs/autoharness: This repo uses Open Knowledge — collaborative markdown via MCP. .open-knowledge/config.yml (with optional /.open-knowledge/config.yml; CLI/env may override) is the path contract: content.dir is the root for relative paths; content.include lists globs that add markdown…

tigerless-labs/autoharness · 2,201 tokens

copilot-tooling AGENTS.md