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/oprogramadorreal/optimus-claude/commitnpx skills add oprogramadorreal/optimus-claude --skill commitgit clone --depth 1 https://github.com/oprogramadorreal/optimus-claudeWhat 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 | $0.00072 | $0.01649 |
| Opus 5 | $0.00036 | $0.00825 |
| Sonnet 5 | $0.00014 | $0.00330 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
commit 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Pick the mode from the arguments: suggest → Suggest mode; branch (optionally followed by a description) → Branch mode; anything else → Default mode.
Multi-repo: if the current directory has no .git/ directory, read $CLAUDE_PLUGIN_ROOT/skills/init/references/multi-repo-detection.md and apply it. In a workspace, git commands run inside each child repo; Default and Suggest modes process each repo with changes independently (per-repo steps, per-repo preview under a ## <repo-name> heading, one combined final summary); Branch mode targets a single repo (its step 1).
Default mode — stage, commit, optionally push
-
Gather changes:
git diff --cached,git diff,git status --short(untracked = names only), leading with--statwhen the diffs are large. In a workspace run these inside each child repo and skip the clean ones. No local changes anywhere → say so and stop. -
Untracked-file gate: if
git status --shortshows untracked files (??):- List them and warn about any that look like secrets (
.env,*.key,*.pem,*.pfx,credentials.*,secrets.*,*.sqlite,*.db). AskUserQuestion— header "Untracked files": "Include all" / "Exclude all" / "Let me choose". "Include all" never covers secret-looking files — each one requires individual confirmation.- Read the contents of the included untracked files — step 1 gathered only their names.
- List them and warn about any that look like secrets (
-
Generate the message: read
$CLAUDE_PLUGIN_ROOT/skills/commit/references/conventional-commit-format.mdand apply it to everything gathered. If changes span multiple concerns,AskUserQuestionwhether to commit together or split; when splitting, run steps 4–6 once per commit with its pre-assigned files. -
Protected-branch check: look for
.claude/hooks/restrict-paths.sh— in a workspace check the child repo first, then the workspace root (first found wins). Parse itsPROTECTED_BRANCHESarray to decide whether the current branch is protected; no hook = unprotected; hook present but array unparseable = treat as unprotected and note it in the preview. If protected, generate a feature branch name per$CLAUDE_PLUGIN_ROOT/skills/commit/references/branch-naming.md—<type>from the commit message, slug from its subject line.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 87 lines · 72 tokens per session scan A 6f143011871e
commit is a skill published in the GitHub repository oprogramadorreal/optimus-claude (73 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 1,649 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…