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 skills add avibebuilder/claude-prime --skill optimus-primegit clone --depth 1 https://github.com/avibebuilder/claude-primeWrote 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/avibebuilder/claude-prime/optimus-prime)<a href="https://agentmods.dev/skills/avibebuilder/claude-prime/optimus-prime"><img src="https://agentmods.dev/badge/skills/avibebuilder/claude-prime/optimus-prime/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/skills/avibebuilder/claude-prime/optimus-prime"><img src="https://agentmods.dev/badge/skills/avibebuilder/claude-prime/optimus-prime.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.00153 | $0.01300 |
| Opus 5 | $0.00077 | $0.00650 |
| Sonnet 5 | $0.00031 | $0.00260 |
| Haiku 4.5 | $0.00015 | $0.00130 |
Grade A, and why
optimus-prime 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 9d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultrathink.
Mission
Generate a Claude configuration that fits the specific project. Every skill, rule, and CLAUDE.md entry must exist because this project needs it — not because a template included it. Analyze the real codebase deeply, understand its conventions and patterns, and build a config that makes Claude work well here.
Modes
- Fresh prime — no claude config yet. Build from scratch.
- Re-prime — claude config already exists. Preserve intentional project work, refresh what is stale or generic, fill gaps.
Default to re-prime whenever meaningful existing config is found. Never overwrite it wholesale without user approval.
Flow
- Analyze the repo deeply — stack, conventions, boundaries, docs, existing config. See analysis-checklist.md.
- Propose findings using the Output Format below. Do not touch meaningful files before approval.
- Create skills via
/skill-creator— every skill must go through skill-creator to ensure quality and project fit. Starters in.claude/starter-skills/are reference input to accelerate creation, not templates to copy. - Generate or refine CLAUDE.md — lean, high-signal, always-on context only. Point to docs/READMEs for detail.
- Rules only if needed — apply the rule test. Zero rules is valid.
- Offer CLAUDE.local.md — personal preferences (role, sandbox URLs, preferred test data, workflow quirks), gitignored.
- Clean up — delete
.claude/starter-skills/after processing. Keep protected skills. Confirm all deletions. - Verify — references resolve, stack claims match evidence, config is project-specific not generic.
- Offer skill optimization — after everything is set up, offer optimization paths sized to how many new skills were created. ≤3 skills: recommend full optimization for all. >3 skills: recommend full optimization for user-designated core skills only + description optimization for the rest (avoids long execution time and token burn). Always emphasize that full optimization takes meaningful time and tokens. Run sequentially — never in parallel; concurrent runs overload the user's machine.
What ships with it
2 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.
- 9d ago First seen · 84 lines · 153 tokens per session scan A 6eafafe0d8c4
optimus-prime is a skill published in the GitHub repository avibebuilder/claude-prime (120 stars, last pushed 3mo ago), licensed MIT. It adds 153 tokens to every session and 1,300 once invoked, about $0.0008 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
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.