What is weekly-git-summary copilot-instructions.md?

Repository-specific instructions for setting up, building, and testing the weekly-git-summary command-line tool.

Use them when installing the project, running its Bun or Node.js build, checking generated files, or following its test process.

They give the coding agent the project’s expected runtimes, dependency commands, build output, and verification checks in one place.

How yinzhenyu-su/weekly-git-summary configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to yinzhenyu-su/weekly-git-summary. 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/yinzhenyu-su/weekly-git-summary/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/yinzhenyu-su/weekly-git-summary

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/yinzhenyu-su/weekly-git-summary/copilot-instructions/github.svg)](https://agentmods.dev/instructions/yinzhenyu-su/weekly-git-summary/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/yinzhenyu-su/weekly-git-summary/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/yinzhenyu-su/weekly-git-summary/copilot-instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/yinzhenyu-su/weekly-git-summary/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/yinzhenyu-su/weekly-git-summary/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,863 This file is loaded in full into every session.

When invoked 1,863 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. ✓ AI security review Sonnet 5 · 7 Sept 2026 📄 Read the review

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.1	$0.01863	$0.01863
Opus 5.5	$0.00745	$0.00745
Sonnet 5.5	$0.00373	$0.00373
Haiku 4.5	$0.00186	$0.00186

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

Security

Grade A, and why

weekly-git-summary 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 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/copilot-instructions.md · 210 lines

How it starts

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

weekly-git-summary Copilot Instructions

Always reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here.

Working Effectively

Environment Setup and Dependencies

Install Node.js ≥22.0.0: curl -fsSL https://nodejs.org/dist/v22.14.0/node-v22.14.0-linux-x64.tar.xz -o node.tar.xz && tar -xf node.tar.xz && sudo cp -r node-v22.14.0-linux-x64/* /usr/local/
Install Bun runtime: curl -fsSL https://bun.sh/install | bash && source ~/.bashrc && export PATH="$HOME/.bun/bin:$PATH"
Install dependencies: bun install (preferred) or npm install (fallback if network issues)
Verify setup: node --version && bun --version

Build Process

Build the CLI tool: bun run build.ts or bun run build
Build time: ~5 seconds. NEVER CANCEL. Set timeout to 60+ seconds.
Output: Creates build/cli.js (main entry), build/weekly-git-summary.js, platform scripts, and HTML template
Verify build: ls -la build/ should show: cli.js, weekly-git-summary.js, weekly-git-summary.sh, weekly-git-summary.ps1, git-log.html

Testing

Run all tests: bun test
Test time: ~4 seconds. NEVER CANCEL. Set timeout to 30+ seconds.
Expected: 40 tests pass, 0 fail
Run specific test suites:
- CLI tests: bun test tests/cli.test.ts
- Build tests: bun test tests/build.test.ts
- Integration tests: bun test tests/integration.test.ts
- Windows tests: bun test tests/windows.test.ts

Linting and Code Quality

Run linting: npm run lint
Fix linting issues: npm run lint:fix
Lint time: ~2 seconds. NEVER CANCEL.
TypeScript check: bun tsc --noEmit

CLI Tool Usage and Validation

Basic CLI Testing

Show help: node build/cli.js --help
Test JSON output: node build/cli.js --dir . --since 2024-01-01 --json
Test Markdown output: node build/cli.js --dir . --since 2024-01-01 --md
Test HTML output: node build/cli.js --dir . --since 2024-01-01 --html
CLI execution time: <2 seconds per command. NEVER CANCEL.

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

2mo ago First seen · 210 lines · 1,863 tokens per session scan F a8dd7c9b1305

Subscribe to this mod's changes

weekly-git-summary copilot-instructions.md is an instructions file published in the GitHub repository yinzhenyu-su/weekly-git-summary (203 stars, last pushed 2mo ago), licensed MIT. It adds 1,863 tokens to every session, about $0.0075 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-30.

bunjs shell-script weekly-reports

weekly-git-summary copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
weekly-git-summary copilot-instructions.mdyinzhenyu-su/weekly-git-summary	Instructions file	203	2mo ago	MIT	A	1,863	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

weekly-git-summary: Instructions file for GitHub Copilot