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/audit-deployed-package)<a href="https://agentmods.dev/skills/runverdict/sf-security-review-toolkit/audit-deployed-package"><img src="https://agentmods.dev/badge/skills/runverdict/sf-security-review-toolkit/audit-deployed-package/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/audit-deployed-package"><img src="https://agentmods.dev/badge/skills/runverdict/sf-security-review-toolkit/audit-deployed-package.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.08486 |
| Opus 5 | $0.00077 | $0.04243 |
| Sonnet 5 | $0.00031 | $0.01697 |
| Haiku 4.5 | $0.00015 | $0.00849 |
Grade A, and why
audit-deployed-package 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 — 512 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Deployed Package
Audit the package the way the reviewer audits it: as an installed artifact in a
real org, not as source on disk. Source reading cannot see what install-time
behavior does to the grants a subscriber actually receives, whether the
post-install handler grants more than the packaged permission sets define,
whether the data-flow engine flags CRUD/FLS on the compiled package, whether the
callouts resolve against org-entered secrets, or whether uninstall leaves the
org clean — and every one of those is a thing the Salesforce reviewer installs your
package to check. This skill runs that pass and folds its findings into the same
ledger the source audit feeds (.security-review/audit-ledger.json), under the
deployed-package dimension, with evidence under
.security-review/evidence/deployed-package/.
Honesty boundary, restated up front (CONVENTIONS §2): this is dynamic verification in a throwaway org — a complementary lens to static source reading, not a stronger one: it previews the reviewer's own install-into-their-org test by really installing and really querying the package, which source on disk cannot do (source cannot verify install-time behavior). But it is still not Salesforce's own penetration test. Salesforce's Product Security team installs your package and tests the surface regardless of anything this pass finds. Nothing here ever earns "will pass." The strongest thing it can say is "no known blockers in what this org let us verify."
When to use
- AFTER
/sf-security-review-toolkit:install-and-verify-packagehas installed a released version into a fresh org and its verification battery is green — that skill solves the hard part (headless install past every SF quirk, the credential config, the permission-chain battery). This skill is the thin security pass on top of an org that is already standing. - As the opt-in deep-audit power-up offered by
/sf-security-review-toolkit:security-review-journeywhensfis authed (or the operator opts to auth) — the journey spins a clean org, installs, runs this, then tears down. Never the always-on core. - After a package upgrade, re-run it: the install-time grant drop and the uninstall residue both change shape across versions.
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 · 512 lines · 153 tokens per session scan A 1953d4266a4f
audit-deployed-package 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 153 tokens to every session and 8,486 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-31.
Other skills, from other repositories
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.
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.
bun-test-lifecycle
Use for test lifecycle hooks: beforeAll, afterAll, beforeEach, afterEach, fixtures, preload.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.