What is Work-Timer CLAUDE.md?

Repository instructions for developing the Work-Timer project, including contribution workflow, testing, documentation, and safety rules. They tell contributors how to make changes without weakening important protections.

Use them when contributing to Work-Timer. They cover task branches, pull requests, tests, builds, focused changes, documentation, and security review.

They provide consistent rules for branch-based development and help prevent unsafe changes to user data, billing, permissions, validation, and destructive actions.

How JoelBondoux/Work-Timer configures Claude Code

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/CLAUDE.md

Clone the repo

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

Made for: Claude Code.

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

Your own site

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

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

When invoked 801 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.00801	$0.00801
Opus 5.5	$0.00320	$0.00320
Sonnet 5.5	$0.00160	$0.00160
Haiku 4.5	$0.00080	$0.00080

Measured 2mo ago against content hash f6887f51f475, 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 CLAUDE.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.

CLAUDE.md · 83 lines

How it starts

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

Claude Instructions for Work-Timer

Repository Workflow

master is the production-ready branch.
Do not commit feature work directly to master.
Create short-lived task branches from master.
Submit a PR back to master.
Ensure npm test and npm run build pass before merge.
Prefer squash merge.

Branch Naming

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

Contribution Standards

Keep PRs scoped to one concern.
Add tests for logic changes.
Update docs for user-facing changes.
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

Run npm test and npm run build before opening or updating a PR.
Run npm run check:production to block debug/dev-only artifacts from release branches.
If files in src/ are changed, regenerate and commit matching dist/ outputs when applicable.
If CLI behavior changes, update docs/cli-reference.md and related setup/readme docs.
If MCP tools are added or changed, update docs/mcp-tools.md to keep tool docs and counts accurate.

Read the full file on GitHub · 83 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 · 83 lines · 801 tokens per session scan A f6887f51f475

Subscribe to this mod's changes

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

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