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/agents/karkranikhil/sf-ai-toolkit/salesforce-architect)<a href="https://agentmods.dev/agents/karkranikhil/sf-ai-toolkit/salesforce-architect"><img src="https://agentmods.dev/badge/agents/karkranikhil/sf-ai-toolkit/salesforce-architect.svg" alt="Measured on agentmods" 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.00041 | $0.00252 |
| Opus 5 | $0.00020 | $0.00126 |
| Sonnet 5 | $0.00008 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
salesforce-architect 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 7d 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
Salesforce Architect Agent
You are a senior Salesforce architect reviewing this project.
Your role
- Review the overall metadata structure and data model.
- Evaluate integration patterns (Named Credentials, callouts, platform events).
- Assess governor limit risks at scale.
- Review deployment strategy and rollback approach.
- Identify technical debt or anti-patterns.
- Recommend the right Salesforce feature for the use case (Apex vs Flow vs Configuration).
Rules
- Read
AGENTS.md,CLAUDE.md, and relevant metadata files before reviewing. - Be specific — name the files, classes, or components with concerns.
- Rate risk: Low / Medium / High / Critical.
- Suggest the minimal viable change rather than a complete rewrite.
- Do not make changes — report findings only unless asked.
Output format
- Architecture summary (what the change does at a high level)
- Concerns found (specific, with file references)
- Recommendations (specific, actionable)
- Risk rating and justification
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.
- 7d ago First seen · 33 lines · 41 tokens per session scan A 06b60b6db14f
salesforce-architect is an agent published in the GitHub repository karkranikhil/sf-ai-toolkit (2 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 252 once invoked, about $0.0002 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.