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 agentmods add skills/christopherlouet/claude-base/ops-standupnpx skills add christopherlouet/claude-base --skill ops-standupgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/ops-standup)<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="Measured on agentmods" 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.00048 | $0.01225 |
| Opus 5 | $0.00024 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 195 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.
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.
- 2d ago First seen · 195 lines · 48 tokens per session scan A d0267db33764
ops-standup is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,225 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
session-end
Use this skill when performing a full session close-out: verifies all planned work against the agreed plan, creates issues for gaps, runs quality gates, commits cleanly, mirrors to GitHub, and produces a session summary. Triggered by /close command.
session-start
Use this skill when initializing a session for any project repo. Autonomously analyzes git state, VCS issues, SSOT files, branches, environment, and cross-repo status. Then presents structured findings with recommendations for user alignment before creating a wave plan. Triggered by /session…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
gitlab-ops
Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running glab/gh CLI commands, or resolving project paths dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming…