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.
npx skills add JHostalek/dotclaude --skill timesheetgit clone --depth 1 https://github.com/JHostalek/dotclaudeWrote 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.
[](https://agentmods.dev/skills/jhostalek/dotclaude/timesheet)<a href="https://agentmods.dev/skills/jhostalek/dotclaude/timesheet"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/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.
<a href="https://agentmods.dev/skills/jhostalek/dotclaude/timesheet"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/timesheet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00012 | $0.00292 |
| Opus 5.5 | $0.00005 | $0.00117 |
| Sonnet 5.5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
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 1mo 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.
What it actually says
Generate a markdown table of the current user's git commits for the requested month, defaulting to the current month.
Data Collection
Repo in working directory. Scope: requested month, defaulting to the current month (1st → now), current user only — filter by git config user.name.
Use local calendar boundaries: midnight on the first day of the requested month through the current time, or the next month’s midnight for a completed month. Calculate dates with calendar-aware arithmetic. Filter the author name literally and exclude merge commits; never construct an invalid date by incrementing the day number.
Output Format
Markdown table, one row per day with commits:
| Day | Summary |
|---|---|
| DD.MM. | Short summary of work themes |
Summary Style
Write like personal shorthand — work-log note, not PR description.
- Group by theme, not by commit. "knowledgebase + RAG tools" over listing each commit separately.
- Target 10-20 words per day (minimum 8, retaining useful context).
- Skip noise: lint fixes, merge commits, trivial reformats — unless they represent significant effort.
- Terse phrasing: "form table extraction + compliance" not "Added form table extraction feature and implemented compliance checks."
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · -1 lines · -12 tokens per session ace683c51493
- 1mo ago First seen · 32 lines · 24 tokens per session scan A 4277e8902a39
timesheet is a skill published in the GitHub repository JHostalek/dotclaude (11 stars, last pushed 3d ago), licensed CC0-1.0. It adds 12 tokens to every session and 292 once invoked, about $0.0000 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.
Other skills, from other repositories
what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise update.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
ln-61-repository-publisher
Commits, pushes and remotely verifies authorized repository changes; does not create releases.
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.