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.
npx agentmods add instructions/techwatching/copilot-goodies/git-commitgit clone --depth 1 https://github.com/TechWatching/copilot-goodiesWhat 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.00551 | $0.00551 |
| Opus 5 | $0.00275 | $0.00275 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
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 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.
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:
- From prompt: Use the issue number if mentioned (e.g., "#123" or "ticket 12345")
- From branch name: Extract from patterns like
feature/123-descriptionorbugfix/AB#123-fix→#123orAB#123 - None found: Proceed without a reference—do not ask for one
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 · 62 lines · 551 tokens per session scan A 76ddc36cf004
copilot-goodies git-commit.instructions.md is an instructions file published in the GitHub repository TechWatching/copilot-goodies (8 stars, last pushed 2mo ago), licensed MIT. It adds 551 tokens to every session, about $0.0028 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.
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.
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).
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.
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).
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.
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.