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 runverdict/sf-security-review-toolkit/plugin install sf-security-review-toolkitWrote 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/runverdict/sf-security-review-toolkit/scope-submission)<a href="https://agentmods.dev/skills/runverdict/sf-security-review-toolkit/scope-submission"><img src="https://agentmods.dev/badge/skills/runverdict/sf-security-review-toolkit/scope-submission/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/runverdict/sf-security-review-toolkit/scope-submission"><img src="https://agentmods.dev/badge/skills/runverdict/sf-security-review-toolkit/scope-submission.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.00090 | $0.11676 |
| Opus 5 | $0.00045 | $0.05838 |
| Sonnet 5 | $0.00018 | $0.02335 |
| Haiku 4.5 | $0.00009 | $0.01168 |
Grade A, and why
scope-submission scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read Grep Glob Write Bash(ls *) Bash(find *) Bash(git ls-files*) Bash(git log *) Bash(git rev-parse *) Bash(sf package *) Bash(sf data query *) Bash(sf project retrieve *) Bash(sf org *) Bash(sf sobject *) How it starts
The opening of the file, as written. The whole thing — 717 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Submission
Establish what is actually being submitted before anything is audited, generated,
or scanned. The output is <target>/.security-review/scope-manifest.json — the
input contract for every downstream skill. A wrong manifest is the most expensive
mistake in the journey: the audit fans out agents against the wrong surface set,
the artifacts describe the wrong architecture, and the DAST scope comes up
narrower than the architecture diagram — which reads to a reviewer as an
incomplete submission. This phase mirrors what Salesforce's own checklist-builder
wizard does (baseline: process-checklist-builder): select architecture
elements, get the requirement list those elements imply.
When to use
- Starting review preparation on a repo with no
.security-review/state - The architecture changed since the last manifest — new endpoints, MCP tools added or removed, a package that grew a UI — re-scope before re-auditing
- NOT for auditing code (
/sf-security-review-toolkit:audit-codebase), running scans (/sf-security-review-toolkit:run-scans), or checking overall progress (/sf-security-review-toolkit:security-review-journey)
Prerequisites
- The partner's repo checked out locally (the
<target>) ${CLAUDE_PLUGIN_ROOT}/baseline/requirements-baseline.yamlreadable- The operator available — half this phase is questions no tool can answer
- Optional: a staging URL for any live MCP server (see step 3 for why staging matters)
- Optional power-up:
sf(Salesforce CLI) installed and authed to the partner's DevHub — with that and operator consent, step 4 auto-resolves a dozen wizard inputs from the Tooling API intosf-autoresolve.json. Absent it the phase still completes; those inputs fall back to operator-asked / code-inferred
Steps
AUTO-MODE LEGIBILITY (an operating rule for every step below). Claude Code
auto mode runs a safety classifier that FAILS CLOSED on compound or opaque
shell it "could not evaluate". When inspecting files or repos, PREFER the
dedicated Read / Grep / Glob tools over compound shell — cd X && grep …
chains, cat pipelines, inline node -e "…", and python3 - <<PY heredocs
are exactly the forms the classifier cannot evaluate and blocks. And run each
prescribed harness command (gate-spec.mjs, record-consent.mjs, the
renders) as its OWN atomic Bash call: one command per call, never &&-chained,
never batched in a for-loop. Atomic invocations evaluate cleanly; compound
ones get denied mid-run and read to the operator as a broken toolkit.
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 · 717 lines · 90 tokens per session scan A 949b77688116
scope-submission is a skill published in the GitHub repository runverdict/sf-security-review-toolkit (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 90 tokens to every session and 11,676 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
researcher
Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth. Use when an album needs factual research, source material, or verification of claims.
validate-album
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
sheet-music-publisher
Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
import-art
Places album art files in the correct audio and content directory locations. Use when the user has generated or downloaded album artwork that needs to be saved.
plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.