A read-only briefing tool for one or more Git repositories. It collects recent commits, pull requests, CI results, blockers, and the day’s priorities.

Use it for daily standups, cross-repository activity summaries, and finding work that needs attention.

It saves developers from checking each repository, pull request, and CI page separately to understand what changed.

ops-standup — Skill for Claude Code by christopherlouet/claude-base

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 christopherlouet/claude-base --skill ops-standup

Clone the repo

git clone --depth 1 https://github.com/christopherlouet/claude-base

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/skills/christopherlouet/claude-base/ops-standup/github.svg)](https://agentmods.dev/skills/christopherlouet/claude-base/ops-standup)

Your own site

<a href="https://agentmods.dev/skills/christopherlouet/claude-base/ops-standup"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/ops-standup/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/skills/christopherlouet/claude-base/ops-standup"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/ops-standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,205 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.00048	$0.01205
Opus 5.5	$0.00019	$0.00482
Sonnet 5.5	$0.00010	$0.00241
Haiku 4.5	$0.00005	$0.00120

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

Security

Grade A, and why

ops-standup 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 25d 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/skills/ops-standup/SKILL.md · 190 lines

How it starts

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

Daily Standup — Morning Briefing

Objective

Scan one or several git repos to generate a structured briefing: recent commits, open PRs, CI state, blockers and priorities of the day.

Read-only mode — no code modification.

Phase 1: Repo detection

Determine the repos to scan

If paths are provided as arguments: use them
If a parent directory is provided: scan 1 level for .git/
Otherwise: use the current directory

Options

Flag	Default	Description
`--since <duration>`	`24h`	Time window (24h, 48h, 7d)
`--summary-only`	no	Short version without per-repo details

Phase 2: Data collection

For each repo, collect:

2.1 Recent commits

# Commits from the last 24h grouped by author
git log --since="24 hours ago" --format="%h %an: %s" --no-merges

Group by author, count commits, identify types (feat/fix/refactor/docs).

2.2 Pull Requests and CI

If gh is available:

# Open PRs
gh pr list --state open --json number,title,author,reviewDecision,statusCheckRollup

# Recently merged PRs
gh pr list --state merged --json number,title,mergedAt --limit 10

Classify the PRs:

To review: reviewDecision = REVIEW_REQUIRED
Approved: reviewDecision = APPROVED (ready to merge)
CI failing: statusCheckRollup contains FAILURE
Pending: statusCheckRollup contains PENDING

2.3 CI state

If gh is available:

# Latest workflow runs
gh run list --limit 10 --json status,conclusion,name,createdAt

Identify:

Failing workflows (conclusion = failure)
Stuck workflows (status = in_progress for > 30 min)
Recently cancelled workflows

2.4 Stale branches

# Branches with no commit for 7+ days (excluding main/develop/release)
git for-each-ref --sort=-committerdate --format='%(refname:short) %(committerdate:relative)' refs/heads/ | grep -E "(weeks|months) ago"

2.5 Uncommitted changes

git status --porcelain

Categorize: staged, unstaged, untracked.

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

25d ago Changed · -4 lines efa8ec05b537
26d ago Changed · -1 lines 26dee5f786ff
1mo ago First seen · 195 lines · 48 tokens per session scan A d0267db33764

Subscribe to this mod's changes

ops-standup is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 1,205 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.

Claude Code Commits Git and workflow Project management agentic-ai ai-coding anthropic claude-ai cli-tool

github-workflow

GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.

Mindrally/skills · 23 tokens

lerna

Best practices for Lerna monorepo management, versioning, and publishing.

Mindrally/skills · 18 tokens

cross-repo-cache

Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…

closedloop-ai/claude-plugins · 81 tokens

core-workflow

Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.

travisjneuman/.claude · 52 tokens

apex-status

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

tonone-ai/tonone · 42 tokens

quick

Execute an ad-hoc task with atomic commits. Skips full plan/review.

SienkLogic/plan-build-run · 19 tokens