agentmods.dev

copilot-goodies: Instructions file for GitHub Copilot

.github/instructions/git-commit.instructions.md

copilot-goodies git-commit.instructions.md is an instructions file for GitHub Copilot from TechWatching/copilot-goodies. It costs 551 tokens per session, scanned A, original, MIT.

A set of rules for writing Git commit messages, which describe changes saved to a code repository.

In plain words
What is it for?
Use it when composing commits that follow Conventional Commits, including allowed change types, optional scopes, imperative wording, and issue references.
Why use it?
It keeps commit history consistent and makes changes easier to understand and search.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

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

not rated 8repo 4mo ago A scan 551 tokens original MIT
View source ↗ TechWatching/copilot-goodies
Reuse

Borrowing it

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

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 copilot-goodies git-commit.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/techwatching/copilot-goodies/git-commit"><img src="https://agentmods.dev/badge/instructions/techwatching/copilot-goodies/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 551 This file is loaded in full into every session.
When invoked 551 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.00551 $0.00551
Opus 5.5 $0.00220 $0.00220
Sonnet 5.5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

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

Security

Grade A, and why

copilot-goodies git-commit.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 2mo 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/instructions/git-commit.instructions.md · 62 lines

How it starts

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

Git Commit Message Guidelines

Format

Commit messages must follow the Conventional Commits specification with an optional issue reference:

<type>(<scope>): <description> (#issue)

Rules

1. Commit Type (Required)

The type must be one of the following:

Type Description
feat A new feature (e.g., a new prompt, instruction, or agent)
fix A bug fix
docs Documentation only changes
style Code style changes (formatting, missing semi-colons, etc)
refactor Code change that neither fixes a bug nor adds a feature
perf Performance improvements
test Adding or updating tests
build Changes to build system or external dependencies
ci Changes to CI configuration files and scripts
chore Other changes that don't modify src or test files
revert Reverts a previous commit

2. Scope (Optional)

  • The scope provides additional context about what part of the codebase is affected
  • Use lowercase, hyphen-separated words
  • Examples: api, auth, db, ui, deps

3. Description

  • Use imperative, present tense: "add" not "added" nor "adds"
  • Don't capitalize the first letter
  • No period at the end
  • Keep it concise but descriptive

4. Issue Reference (Recommended)

Append the issue or work item number to the commit message using this priority:

  1. From prompt: Use the issue number if mentioned (e.g., "#123" or "ticket 12345")
  2. From branch name: Extract from patterns like feature/123-description or bugfix/AB#123-fix → #123 or AB#123
  3. None found: Proceed without a reference—do not ask for one

Read the full file on GitHub · 62 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. 2mo ago First seen · 62 lines · 551 tokens per session scan A 76ddc36cf004

Subscribe to this mod's changes

copilot-goodies git-commit.instructions.md is an instructions file published in the GitHub repository TechWatching/copilot-goodies (8 stars, last pushed 4mo ago), licensed MIT. It adds 551 tokens to every session, about $0.0022 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-31.

CommitsGit and workflow
Related

copilot-goodies git-commit.instructions.md compared with instructions from other repositories

copilot-goodies git-commit.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
copilot-goodies git-commit.instructions.mdTechWatching/copilot-goodiesInstructions file84mo agoMITA551GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode