A command that builds a timesheet summary from Git commits and file changes. It groups activity into work categories and estimates time for a chosen period.

Use it to prepare weekly, monthly, or custom-period timesheets in summary or detailed format.

It turns scattered project history into a work record, reducing the need to reconstruct hours manually. Estimates with weak evidence are flagged.

timesheet — Command for Claude Code by mizukaizen

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.

Clone the repo

git clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcp

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/commands/mizukaizen/hive-doctrine-mcp/timesheet/github.svg)](https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/timesheet)

Your own site

<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/timesheet"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/timesheet/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/commands/mizukaizen/hive-doctrine-mcp/timesheet"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/timesheet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 504 The whole file, excluding the scripts and references it only reads on demand.

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.00000	$0.00504
Opus 5	$0.00000	$0.00252
Sonnet 5	$0.00000	$0.00101
Haiku 4.5	$0.00000	$0.00050

Measured 12d ago against content hash 18ce76cb5363, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

timesheet 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 12d 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.

gated-products/honey/claude-packages/HD-4005-consultant/commands/timesheet.md · 74 lines

How it starts

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

/timesheet

Generate a timesheet summary from git commits and file modification history.

Usage

/timesheet [--period "YYYY-WNN"|"YYYY-MM"|"YYYY-MM-DD to YYYY-MM-DD"] [--format summary|detailed]

Behaviour

1. Gather Activity Data

Run git log for the specified period with timestamps and file changes.
Scan file modification times in the project directory.
Cross-reference with any existing timesheet entries in timesheets/.

2. Categorise Work

Map each commit and file change to a category:

Category	Indicators
Research	Files in `data/`, web research notes, source documents
Analysis	Files in `analysis/`, spreadsheets, data processing scripts
Writing	Files in `deliverables/`, report drafts, memos
Review	Commits with "review", "revise", "feedback" in messages
Meetings	Meeting notes, agenda files
Admin	Config files, project setup, housekeeping

3. Estimate Hours

Estimate work time based on gaps between commits and file modifications.
Round to nearest 15-minute increment.
Cap any single session at 4 hours unless evidence suggests continuous work.
Flag estimates with low confidence (large gaps between activity, ambiguous categorisation).

4. Generate Summary

Summary format:

# Timesheet: [Period]

## Summary
| Category | Hours | % of Total |
|----------|-------|-----------|
| Research | X.XX | XX% |
| Analysis | X.XX | XX% |
| Writing | X.XX | XX% |
| Review | X.XX | XX% |
| Admin | X.XX | XX% |
| **Total** | **X.XX** | **100%** |

## By Deliverable
| Deliverable | Hours |
|------------|-------|
| [Name] | X.XX |

## Notes
- [Any estimation caveats]

Detailed format: Adds a day-by-day breakdown with individual entries.

5. Save

Write the timesheet to timesheets/[period].md.

Notes

These are estimates based on available signals. Always review before submitting to a client.
The tool cannot capture work done outside the project directory (calls, whiteboard sessions, etc.). Add those manually.

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

12d ago First seen · 74 lines · 0 tokens per session scan A 18ce76cb5363

Subscribe to this mod's changes

timesheet is a command published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 504 tokens. 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.

AI Safety Git and workflow Multi-Agent Productivity agent-marketplace ai-agents mcp mcp-server

save

Save current session. Writes a session log with what was done, decisions made, and what's pending. Optional: commit & push.

avelikiy/great_cto · 26 tokens

acos-checkpoint

Create checkpoints before risky operations. Rollback if things go wrong.

frankxai/agentic-creator-os · 0 tokens

release-flow

Portable gated release flow — deterministic gate + vendor-agnostic independent reviewer, runnable from any harness.

coo1white/cool-workflow · 20 tokens

mega-approve

Approve the mega-plan and start feature execution. Creates worktrees and generates PRDs for each feature. Usage: /plan-cascade:mega-approve [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--auto-prd] [--agent ] [--prd-agent ] [--impl-agent ].

Taoidle/plan-cascade · 110 tokens

worktree

Start a new task in an isolated Git worktree for parallel multi-task development. Creates a task branch, worktree directory with planning files, and leaves the main directory untouched. Usage: /plan-cascade:worktree [task-name] [target-branch]. Example: /plan-cascade:worktree feature-login main.

Taoidle/plan-cascade · 65 tokens

release

Prepare a release (step 1 of 2) — version bump and PR. Cutting the tag is a separate operator-only step.

coo1white/cool-workflow · 27 tokens