What is Work-Timer copilot-instructions.md?

Repository instructions for developing the Work-Timer project, including branch rules, testing requirements, and safety guidelines. A branch is a separate line of development used to keep unfinished changes away from the production-ready branch.

Use them when making changes to Work-Timer. They cover naming task branches, opening pull requests, running tests and builds, keeping changes focused, and protecting user data.

They help contributors avoid changing the production branch directly and preserve safety checks around timer, billing, export, and destructive operations.

How JoelBondoux/Work-Timer configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to JoelBondoux/Work-Timer. 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/JoelBondoux/Work-Timer/master/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/JoelBondoux/Work-Timer

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/joelbondoux/work-timer/copilot-instructions/github.svg)](https://agentmods.dev/instructions/joelbondoux/work-timer/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/joelbondoux/work-timer/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/joelbondoux/work-timer/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/joelbondoux/work-timer/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/joelbondoux/work-timer/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Model	Per session	Once invoked
Fable 5.1	$0.00851	$0.00851
Opus 5.5	$0.00340	$0.00340
Sonnet 5.5	$0.00170	$0.00170
Haiku 4.5	$0.00085	$0.00085

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

Security

Grade A, and why

Work-Timer 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 · 82 lines

How it starts

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

Copilot Instructions for Work-Timer

Repository Workflow

Treat master as production-ready at all times.
Never perform feature development directly on master.
Create a short-lived branch from master for each task.
Open a PR to merge back into master.
Merge only after checks pass (npm test and npm run build).
Prefer squash merge.

Branch Naming

feature/<short-description>
fix/<short-description>
chore/<short-description>

Development Guardrails

Keep changes focused and minimal.
Do not bypass safety behavior in timer, billing, export, or destructive flows.
Preserve current CLI and MCP behavior unless the task explicitly changes it.
For user-facing PowerShell/terminal output formatting, follow docs/powershell-output-style-guide.md as the default standard for current and future output UX changes.

Safety And Security First Policy

Treat user data protection, billing correctness, and destructive-operation safety as top priority over speed.
Default to least-privilege and non-destructive behavior: prefer dry-run, explicit confirmations, and reversible changes.
Never weaken or bypass safety checks, authorization boundaries, or validation logic unless explicitly required and documented.
If a change introduces meaningful security, privacy, or integrity risk, stop and escalate with options, risks, and a recommended safe default.
Call out security-impacting changes in PR summaries and include focused validation steps.

Local Staging Workspace Rules

Use staging/ for local-only test notes, debug helpers, and temporary artifacts.
Treat staging/ as non-production and non-release content.
Do not commit files from staging/.
Do not reference staging/ as a required documentation location; durable docs must live under docs/.

Required Validation Before PR

Run npm test and npm run build.
Run npm run check:production to catch debug/dev-only artifacts before merge.
If source files change under src/, ensure generated outputs under dist/ are regenerated and committed when applicable.
If CLI command behavior changes, update docs in docs/cli-reference.md and relevant setup/readme pages.
If MCP tools change, update docs/mcp-tools.md to keep tool docs and counts accurate.

Read the full file on GitHub · 82 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 · 82 lines · 851 tokens per session scan A 8057992f3401

Subscribe to this mod's changes

Work-Timer copilot-instructions.md is an instructions file published in the GitHub repository JoelBondoux/Work-Timer (0 stars, last pushed 2d ago), licensed MIT. It adds 851 tokens to every session, about $0.0034 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.

Git and workflow

Work-Timer copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Work-Timer copilot-instructions.mdJoelBondoux/Work-Timer	Instructions file	0	2d ago	MIT	A	851	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	yesterday	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

Work-Timer: Instructions file for GitHub Copilot