start-of-day

start-of-day is a skill for Claude Code from Claude-Code-Community-Ireland/claude-code-resources. It costs 50 tokens per session (874 once invoked), scanned A, original, MIT.

A daily project check-in that reviews Git repositories, code, documentation, and unfinished tasks.

In plain words
What is it for?
Use it to inspect repository status, understand a project's structure, review documentation, and identify next steps.
Why use it?
It replaces a manual morning review with one status summary showing what changed, what exists, and what remains.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the TodoWrite tool.

Part of the vibeworks-library plugin — 34 skills, 21 commands, 33 agents, 3 hooks shipped together

Good fit Use it to inspect repository status, understand a project's structure, review documentation, and identify next steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/claude-code-community-ireland/claude-code-resources/start-of-day
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 Claude-Code-Community-Ireland/claude-code-resources --skill start-of-day
Clone the repo
git clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resources

Made for: Claude Code.

Or install vibeworks-library, the plugin that ships this one along with the rest of its 34 skills, 21 commands, 33 agents, 3 hooks.

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 start-of-day

README.md
[![agentmods](https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/start-of-day/github.svg)](https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/start-of-day)
Your own site
<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/start-of-day"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/start-of-day/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 start-of-day

Your own site · 80×15
<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/start-of-day"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/start-of-day.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 874 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.00050 $0.00874
Opus 5.5 $0.00020 $0.00350
Sonnet 5.5 $0.00010 $0.00175
Haiku 4.5 $0.00005 $0.00087

Measured 1mo ago against content hash b4844d6d9755, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

start-of-day 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.

plugins/vibeworks-library/skills/start-of-day/SKILL.md · 140 lines

How it starts

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

Start of Day - Universal Project Sync

This skill performs a comprehensive analysis of the current working directory to get you synced up at the start of each day. It works on any project.

What This Skill Does

  1. Git Repository Check

    • Detects if current directory is a git repo
    • Fetches and pulls latest changes if behind
    • Reports current branch and status
    • Shows recent commits
  2. Codebase Analysis

    • Reads all key files in the project
    • Identifies tech stack and architecture
    • Reviews project structure
    • Identifies what's built vs pending
  3. Documentation Review

    • Reads all markdown files
    • Reviews any documentation folders
    • Identifies action items and TODOs
  4. Status Report

    • Git sync summary
    • Project overview
    • Key files and structure
    • Recommended next steps

Execution Steps

Step 1: Git Repository Check

Check if the current working directory (or any subdirectories) contains git repos:

# Check if current directory is a git repo
git status 2>/dev/null

# If it's a repo, fetch and check status
git fetch origin 2>/dev/null
git status -sb

# Check if behind remote
git rev-list HEAD..@{u} --count 2>/dev/null

# Pull if behind
git pull

# Show recent commits
git log --oneline -10

If the current directory is not a git repo, check subdirectories for git repos and report on each.

Step 2: Read Project Files

Read key files to understand the project:

  1. Configuration files (use Glob to find, then Read):

    • package.json, requirements.txt, Cargo.toml, etc.
    • .env.example, config files
    • README.md, CONTRIBUTING.md
  2. Source code structure (use Glob):

    • Find main entry points
    • Identify src/lib/app directories
    • Map out the project structure
  3. Documentation (use Glob + Read):

    • All *.md files
    • Any docs/ folder contents
    • Implementation plans, specs

Step 3: Codebase Exploration

Use the Explore agent to thoroughly analyze the codebase:

  • Technology stack (frameworks, languages)
  • Project architecture
  • Key components and their purposes
  • Dependencies and their versions
  • What's implemented vs TODO comments

Read the full file on GitHub · 140 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. 1mo ago First seen · 140 lines · 50 tokens per session scan A b4844d6d9755

Subscribe to this mod's changes

start-of-day is a skill published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 874 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-09-03.

Related

Other skills, from other repositories

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

cuga-github-issues

Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…

cuga-project/cuga-agent · 88 tokens