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.
git 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/commands/christopherlouet/claude-base/ops-standup)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-standup"><img src="https://agentmods.dev/badge/commands/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.
<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-standup"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-standup.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.00000 | $0.00302 |
| Opus 5.5 | $0.00000 | $0.00121 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 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
OPS-STANDUP Agent
Morning briefing: commits, PRs, CI, blockers and priorities of the day.
Request context
$ARGUMENTS
Objective
Generate a structured cross-repo briefing covering recent activity, PR and CI state, blockers, and suggested priorities.
Use the ops-standup skill for the detailed methodology.
Workflow
- Detect repos to scan (arguments, current directory, or parent scan)
- Collect recent commits, open/merged PRs, CI state, stale branches
- Synthesize into 4 categories: done, in progress, blocked, priorities
- Generate the technical report (or summary with
--summary-only)
Expected output
- Recent activity: commits per author, merged PRs
- PR state: to review, approved, CI failing
- CI Health: failing or blocked workflows
- Priorities of the day: actions to take first
Related agents
| Agent | Usage |
|---|---|
/ops:ops-health |
Full project health check |
/ops:ops-ci-fix |
Fix failing CI pipelines |
/ops:ops-deps |
Check dependencies |
IMPORTANT: Read-only mode — never modify files or PRs.
YOU MUST clearly signal if gh CLI is not available.
NEVER invent data — flag the gaps.
Think hard about priorities and provide concrete actions for the day.
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 First seen · 46 lines · 0 tokens per session scan A 426f91f4cf41
ops-standup is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 302 tokens. 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 commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.