recording-work-time

recording-work-time is a skill for Claude Code, Codex from Odalrick/estimate-maestro. It costs 56 tokens per session (1,423 once invoked), scanned A, original, MIT.

A mechanical time-tracking guide for recording work on a tracked effort and its work slices.

In plain words
What is it for?
Use it when starting or stopping tracked work, recording meetings or slice insertions, closing slices, or running a retrospective plan pass.
Why use it?
It keeps clocking in, clocking out, adding work slices, and closing them against pull requests consistent with the tracking process.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when starting or stopping tracked work, recording meetings or slice insertions, closing slices, or running a retrospective plan pass.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/odalrick/estimate-maestro/recording-work-time
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.

Any agent
npx skills add Odalrick/estimate-maestro --skill recording-work-time
Clone the repo
git clone --depth 1 https://github.com/Odalrick/estimate-maestro

Made for: Claude Code, Codex.

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.

agentmods badge for recording-work-time

README.md
[![agentmods](https://agentmods.dev/badge/skills/odalrick/estimate-maestro/recording-work-time/github.svg)](https://agentmods.dev/skills/odalrick/estimate-maestro/recording-work-time)
Your own site
<a href="https://agentmods.dev/skills/odalrick/estimate-maestro/recording-work-time"><img src="https://agentmods.dev/badge/skills/odalrick/estimate-maestro/recording-work-time/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.

agentmods 80×15 button for recording-work-time

Your own site · 80×15
<a href="https://agentmods.dev/skills/odalrick/estimate-maestro/recording-work-time"><img src="https://agentmods.dev/badge/skills/odalrick/estimate-maestro/recording-work-time.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,423 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.01423
Opus 5.5 $0.00022 $0.00569
Sonnet 5.5 $0.00011 $0.00285
Haiku 4.5 $0.00006 $0.00142

Measured 13d ago against content hash 79527aae8d93, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

recording-work-time 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 13d 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.

skills/recording-work-time/SKILL.md · 100 lines

How it starts

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

Recording work time

Strict and mechanical. Do these things at these moments. No judgement calls, no interpretation, no estimation reasoning — this skill exists so that referencing it does not pull estimation ideas into a working session.

Starting an effort

start_effort(title, kind, plan_path, summary_text, optimistic, likely, pessimistic, rationale, work_slices) creates the effort and takes the plan's slice titles up front, as work_slices, a list of titles. This is not incidental: the initial slice count is what makes later drift measurable. Do not create the effort with an empty slice list and add slices afterwards to get to the plan's real inventory — that throws away the baseline. Once the effort is under way, add_slice is for slices that were not in that original list — scope growth, not initial setup.

When to clock in

  • Starting work on a slice: clock_in(effort, work_slice).
  • Starting effort-level work with no slice — a design conversation, a retrospective: clock_in(effort).
  • A meeting that is part of the work: clock_in(effort, kind="meeting", internal=<people we pay for, including the user>, external=<people we do not>, participants=<names, if known now>).

clock_in refuses when an interval is already open. That refusal is correct; clock out first rather than working around it.

clock_in also refuses when work_slice is given but is not a live slice on that effort — dropped, or simply mistyped — raising UnknownSlice. A stale slice identifier is a plausible mistake mid-effort; treat the refusal as a prompt to check the identifier, not as something to route around. A closed slice is still clockable, deliberately: a merged pull request can still need post-merge fixes, and that time belongs to the slice it came from.

If the names were not to hand when clocking into the meeting, participants can be left out and attached later — or corrected — with annotate_interval(effort, interval, internal=, external=, participants=, note=). It works on any interval, not only meetings, and is also the way to attach a note after the fact.

Read the full file on GitHub · 100 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. 13d ago Changed · -15 lines 79527aae8d93
  2. 2mo ago First seen · 115 lines · 56 tokens per session scan A fc72db3f3214

Subscribe to this mod's changes

recording-work-time is a skill published in the GitHub repository Odalrick/estimate-maestro (0 stars, last pushed 14d ago), licensed MIT. It adds 56 tokens to every session and 1,423 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

OpenSourceManagement

Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…

danielmiessler/LifeOS · 212 tokens

gsd-ns-manage

Invoke this Pi skill with /skill:gsd-ns-manage.

open-gsd/gsd-core · 16 tokens

feature-prioritisation

Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…

mohitagw15856/pm-claude-skills · 103 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

to-spec

A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.

vinvcn/mattpocock-skills-zh-CN · 29 tokens

cs-escalation-brief

Redacta un informe de escalada estructurado para una cuenta de cliente en riesgo. Úsalo cuando una cuenta haya escalado, cuando un cliente amenace con cancelar, cuando un problema de cliente P1 requiera atención ejecutiva, o cuando prepares un plan de retención interno. Produce un informe de escalada preciso con…

mohitagw15856/pm-claude-skills · 94 tokens