logout

logout is a command for Claude Code from forcedotcom/sf-skills. It costs 20 tokens per session (352 once invoked), scanned A, original, Apache-2.0.

A sign-out command for Salesforce orgs, which are separate Salesforce environments such as production accounts or sandboxes. It can log out of one named org or all authenticated orgs.

In plain words
What is it for?
Logging out of a selected Salesforce org, logging out of every connected org, and checking which orgs are currently authenticated.
Why use it?
It removes saved access when you no longer want this computer connected to an org. It asks for confirmation because logging out means you must authenticate again before using that org.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the salesforce-development plugin — 37 skills, 14 commands, 1 agent, 3 MCP servers shipped together

Good fit Logging out of a selected Salesforce org, logging out of every connected org, and checking which orgs are currently authenticated.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/forcedotcom/sf-skills/logout
About the project

forcedotcom/sf-skills is a collection of reusable instructions that help AI coding agents build and work with Salesforce applications and platform features. Developers use it for Agentforce agents, Lightning apps, Flow, Apex, SOQL, Lightning Web Components, and related Salesforce configuration. The catalogue entries are the repository’s skills, plugins, commands, MCP servers, and agents for AI tools that support skills.

forcedotcom/sf-skills · 1,104 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/forcedotcom/sf-skills

Made for: Claude Code.

Or install salesforce-development, the plugin that ships this one along with the rest of its 37 skills, 14 commands, 1 agent, 3 MCP servers.

Wrote 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.

agentmods badge for logout

README.md
[![agentmods](https://agentmods.dev/badge/commands/forcedotcom/sf-skills/logout/github.svg)](https://agentmods.dev/commands/forcedotcom/sf-skills/logout)
Your own site
<a href="https://agentmods.dev/commands/forcedotcom/sf-skills/logout"><img src="https://agentmods.dev/badge/commands/forcedotcom/sf-skills/logout/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.

agentmods 80×15 button for logout

Your own site · 80×15
<a href="https://agentmods.dev/commands/forcedotcom/sf-skills/logout"><img src="https://agentmods.dev/badge/commands/forcedotcom/sf-skills/logout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 352 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00352
Opus 5.5 $0.00008 $0.00141
Sonnet 5.5 $0.00004 $0.00070
Haiku 4.5 $0.00002 $0.00035

Measured 18d ago against content hash a89a31af587b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

logout 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 18d 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.

plugins/builder/salesforce-development/commands/logout.md · 34 lines

What it actually says

Log out of one or more Salesforce orgs.

Workflow:

  1. Parse arguments ($ARGUMENTS):

    • --target-org <alias> → log out of a specific org
    • --all → log out of every authenticated org
    • No arguments → list current orgs and ask which to log out of
  2. If no arguments: call sf org list --skip-connection-status --json (skip the per-org token refresh), present the orgs in a numbered list, and ask the user which to log out of.

  3. Confirm before action: show the alias(es) about to be logged out and require explicit "yes" confirmation. This is destructive and the user will need to re-authenticate to use the org again.

  4. Run the logout:

    sf org logout --target-org <alias> --no-prompt
    # or
    sf org logout --all --no-prompt
    
  5. Report: confirm which orgs are now logged out. If the project's current target-org was logged out, suggest the user pick a new default via /salesforce-development:set-default <alias> or authenticate fresh via /salesforce-development:login.

Rules:

  • ALWAYS confirm before logging out
  • NEVER log out without explicit user input (no auto-cleanup)
  • If the user logs out of the target-org, their next deploy/data command will fail until they reconfigure
Changes

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.

  1. 18d ago Changed a89a31af587b
  2. 1mo ago First seen · 34 lines · 20 tokens per session scan A 4c48c0305c99

Subscribe to this mod's changes

logout is a command published in the GitHub repository forcedotcom/sf-skills (1,104 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 352 once invoked, about $0.0001 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-09-03.