agentmods.dev

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.

In plain words
What is it for?
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.
Why use it?
They help contributors avoid changing the production branch directly and preserve safety checks around timer, billing, export, and destructive operations.

Instructions file for GitHub Copilot

0 8d ago A scan 851 tokens original MIT
View the source file JoelBondoux/Work-Timer
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/joelbondoux/work-timer/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/JoelBondoux/Work-Timer

Made for: GitHub Copilot.

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. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00851 $0.00851
Opus 5 $0.00426 $0.00426
Sonnet 5 $0.00170 $0.00170
Haiku 4.5 $0.00085 $0.00085

Measured yesterday against content hash 8057992f3401, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

  1. yesterday 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 8d ago), licensed MIT. It adds 851 tokens to every session, about $0.0043 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.

Git and workflowSecurityTesting
Related

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.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

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.

github/spec-kit · 7,104 tokens

langchain AGENTS.md

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.

langchain-ai/langchain · 4,345 tokens