Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tsmztech/claude-code-plugins/plugin install salesforce-devWrote 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/tsmztech/claude-code-plugins/apex-code-review)<a href="https://agentmods.dev/skills/tsmztech/claude-code-plugins/apex-code-review"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/apex-code-review/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/tsmztech/claude-code-plugins/apex-code-review"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/apex-code-review.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.00149 | $0.02663 |
| Opus 5.5 | $0.00060 | $0.01065 |
| Sonnet 5.5 | $0.00030 | $0.00533 |
| Haiku 4.5 | $0.00015 | $0.00266 |
Grade A, and why
apex-code-review 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 2mo 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apex Code Review
Perform a structured, severity-categorized code review of Apex classes, triggers, and test classes against Salesforce best practices, security guidelines, governor limit awareness, and design patterns.
Phase 1: Your FIRST action -- ask where to get the source code
Before doing ANYTHING else -- before searching, before reading files, before any Glob calls -- you must ask the user where the Apex source code is located. This is your first action every time because class names alone don't tell you whether the files exist locally or need to be fetched from a Salesforce org.
What NOT to do (common failure)
❌ WRONG: User says "review AccountService" → you immediately run Glob to search
for the file → file not found → you ask user to paste code or give a path.
This wastes time and misses the Salesforce org fetch entirely.
What to do instead
✅ RIGHT: User says "review AccountService" → you FIRST ask where to get the file
→ user says "Salesforce org" → you run fetch-apex.js → you have the code.
Step 1: Collect file/class names
Determine which files to review from the request:
$ARGUMENTScontains file paths or class names → use those- User has an IDE selection → review that code directly (skip Step 2)
- Neither → ask the user which files to review
Step 2: Ask source preference using AskUserQuestion
Use AskUserQuestion to ask where to get the source code. Here is the exact question to ask -- do not skip this, do not try to find the files first:
question: "Where should I get the Apex source code?"
options:
- label: "Search locally"
description: "I'll search for the files in the current project directory"
- label: "Fetch from Salesforce org"
description: "I'll retrieve the source code from your connected Salesforce org"
Skip this question ONLY if one of these is true:
- The user gave full file paths (e.g.,
force-app/.../AccountService.cls) - The user has code selected in their IDE
- The user explicitly said "from org" or "from salesforce" in their message
What ships with it
1 file 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.
- 2mo ago First seen · 331 lines · 149 tokens per session scan A c48b396e83c5
apex-code-review is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 149 tokens to every session and 2,663 once invoked, about $0.0006 per session on Opus 5.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-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…