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.
git clone --depth 1 https://github.com/karkranikhil/sf-ai-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/commands/karkranikhil/sf-ai-toolkit/review-security)<a href="https://agentmods.dev/commands/karkranikhil/sf-ai-toolkit/review-security"><img src="https://agentmods.dev/badge/commands/karkranikhil/sf-ai-toolkit/review-security/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/commands/karkranikhil/sf-ai-toolkit/review-security"><img src="https://agentmods.dev/badge/commands/karkranikhil/sf-ai-toolkit/review-security.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.00000 | $0.00243 |
| Opus 5.5 | $0.00000 | $0.00097 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
review-security 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.
What it actually says
/review-security
Review the changed files in this project for Salesforce security issues.
What to check
- SOQL injection — dynamic SOQL without
escapeSingleQuotesor bind variables - CRUD/FLS — all DML and queries enforce appropriate object and field permissions
- Sharing — all Apex classes use
with sharing(or have documented exceptions) - Secrets — no tokens, credentials, session IDs, JWTs, or private keys in code or metadata
- Named Credentials — all external callouts use Named Credentials
- Guest user — no sensitive data accessible without authentication
- Hardcoded IDs — no hardcoded org IDs, record IDs, or user IDs
- Permissions — no over-privileged Permission Set assignments
Output format
For each file reviewed:
- List any security issues found (severity: Critical / High / Medium / Low)
- Provide the specific line or code that is the concern
- Suggest the fix
End with a summary table: File | Issues Found | Severity.
If no issues found, state clearly: "No security issues found."
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 · 26 lines · 0 tokens per session scan A d446f3f2fc6d
review-security is a command published in the GitHub repository karkranikhil/sf-ai-toolkit (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 243 tokens. 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.
review-security compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| review-securitykarkranikhil/sf-ai-toolkit | Command | 2 | 6mo ago | MIT | A | 0 | Claude Code |
| diff-reviewcoco-research/coco | Command | 785 | yesterday | Apache-2.0 | A | 11 | Claude Code |
| review-branchdamusix/atomic-claude | Command | 115 | 5d ago | MIT | A | 35 | Claude Code |
| refactorRchGrav/claudebox | Command | 1.2k | 1mo ago | MIT | A | 9 | Claude Code |
| spec-trace-requirementsrjmurillo/ai-agents | Command | 49 | yesterday | MIT | A | 0 | GitHub Copilot |
| merge-conflict-analysisrjmurillo/ai-agents | Command | 49 | yesterday | MIT | A | 0 | GitHub Copilot |
| initazrtydxb/procoder | Command | 211 | 11d ago | Apache-2.0 | A | 16 | Claude Code |