cpu

cpu is a command for Claude Code from KaimingWan/oh-my-kiro. It costs 0 tokens per session (1,039 once invoked), scanned A, original, MIT.

A workflow for committing all current project changes, pushing the branch to its remote repository, and updating the README when new files need listing.

In plain words
What is it for?
Use it at the end of a change to review affected files, add missing command or skill entries, create a commit, and push it.
Why use it?
It checks documentation and completes the common steps after development work, reducing forgotten README entries or unpushed commits.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions AGENTS.md.

Good fit Use it at the end of a change to review affected files, add missing command or skill entries, create a commit, and push it.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kaimingwan/oh-my-kiro/cpu
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.

Clone the repo
git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro

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.

agentmods badge for cpu

README.md
[![agentmods](https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/cpu.svg)](https://agentmods.dev/commands/kaimingwan/oh-my-kiro/cpu)
Your own site
<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/cpu"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/cpu.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,039 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.00000 $0.01039
Opus 5 $0.00000 $0.00519
Sonnet 5 $0.00000 $0.00208
Haiku 4.5 $0.00000 $0.00104

Measured 7d ago against content hash 0d0261e5ba53, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

cpu 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 7d 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.

commands/cpu.md · 113 lines

How it starts

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

Commit all changes, push to remote, and complete branch lifecycle. (CPU = Commit Push Update-readme)

Scope

Only operate on the current project (where AGENTS.md lives). NEVER cd into or commit/push other repositories.

Steps

Step 0: Update README (the "U" in CPU)

Before committing, check if README.md needs updating based on what changed.

  1. Run git diff --name-only HEAD (or git diff --name-only --cached HEAD if staged) to get changed files.

  2. Check each category against README.md:

Changed path pattern README section to check
commands/*.md (new file) Command table (@command rows)
skills/*/SKILL.md (new file) Skills table or list
hooks/**/*.sh (new file) Hooks section or directory tree
Any new top-level directory Directory tree in README
  1. For each mismatch found:

    • Read the new file to understand what it does (first line or description field)
    • Add the missing entry to the appropriate README section
    • Match the format of existing entries exactly
  2. If no README updates needed, skip silently. If updates were made, stage them with the rest.

Rule: Only ADD entries for new files. Do NOT rewrite, reformat, or "improve" existing README content.

Step 1: Stage & Commit

  1. git add -A && git status --short — show what's staged
  2. Ask user for commit message if not provided, or generate one from the diff
  3. git commit -m "<message>"
  4. git push
  5. Report: commit hash + push result

Step 2: Detect Worktree

Check if currently inside a git worktree:

wt_dir=$(git rev-parse --git-common-dir 2>/dev/null)
git_dir=$(git rev-parse --git-dir 2>/dev/null)
if [ "$wt_dir" != "$git_dir" ]; then
  echo "IN_WORKTREE=true"
  # Get the base branch (the branch of the main working tree)
  base_branch=$(git -C "$wt_dir/.." branch --show-current 2>/dev/null || echo "main")
  echo "BASE_BRANCH=$base_branch"
else
  echo "IN_WORKTREE=false"
fi
  • If not in worktree → STOP here. Done (original behavior).
  • If in worktree → continue to Step 3.

Read the full file on GitHub · 113 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. 7d ago First seen · 113 lines · 0 tokens per session scan A 0d0261e5ba53

Subscribe to this mod's changes

cpu is a command published in the GitHub repository KaimingWan/oh-my-kiro (103 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,039 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-08-30.