agentmods.dev

sf-session-extract

sf-session-extract is a skill for Claude Code from divingsbysangam/salesforce-compound-engineering-plugin. It costs 35 tokens per session (464 once invoked), scanned A, a copy of sf-release-notes, MIT.

A helper that extracts the main events and error signals from one Claude, Codex or Cursor session file. It recognises several Salesforce-related errors, such as deployment failures and governor-limit problems.

In plain words
What is it for?
Use it when examining a single coding-agent session to find what happened, which tools were used, what decisions were made and where Salesforce-specific errors occurred.
Why use it?
Long session transcripts are difficult to inspect manually. The helper produces a shorter view of tool calls, decisions and important failures.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool; mentions Claude Code.

Part of the sf-compound-engineering plugin — 68 skills, 1 hook, 2 MCP servers shipped together

not rated 10repo 3d ago A scan 35 tokens copy · 89% MIT

Good fit Use it when examining a single coding-agent session to find what happened, which tools were used, what decisions were made and where Salesforce-specific errors occurred.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-session-extract
View source ↗ divingsbysangam/salesforce-compound-engineering-plugin
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.

Any agent
npx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-session-extract
Clone the repo
git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-plugin

Made for: Claude Code.

Or install sf-compound-engineering, the plugin that ships this one along with the rest of its 68 skills, 1 hook, 2 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 sf-session-extract

README.md
[![agentmods](https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-session-extract.svg)](https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-session-extract)
Your own site
<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-session-extract"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-session-extract.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 464 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 89% copy Near-identical to another mod 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.00035 $0.00464
Opus 5 $0.00017 $0.00232
Sonnet 5 $0.00007 $0.00093
Haiku 4.5 $0.00003 $0.00046

Measured 7d ago against content hash 38d5d66e2421, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

sf-session-extract 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.

Origin

This is a copy

89% identical to sf-release-notes — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/sf-session-extract/SKILL.md · 37 lines

What it actually says

sf-session-extract

Parse a session transcript for tool calls, error signatures, and decisions, returning a compact skeleton.

<feature_description> #$ARGUMENTS </feature_description>

Salesforce Angle

  • Recognize Salesforce-specific error signatures (governor limits, deploy failures, FLS errors, callout failures) and surface them prominently.

Interaction Method

When asking the user a question, use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini). Fall back to numbered options in chat when no blocking tool is available. Ask one question at a time. Prefer concise single-select choices when natural options exist.

Procedure

This skill follows the standard sf-compound-engineering execution discipline:

  1. Understand the input — read the <feature_description> block above and any referenced files, plans, or issues.
  2. Plan a small set of phases — break the work into 2-5 ordered steps that an implementer (or another skill) can verify.
  3. Apply the Salesforce Angle notes above — these encode the platform-specific considerations (governor limits, sharing context, deploy ordering, FLS, metadata semantics) that distinguish this skill from generic counterparts.
  4. Use Salesforce-aware contexts and commands — file paths under force-app/main/default/..., test commands like sf apex run test, deploy commands like sf project deploy validate and sf project deploy start, query the org with sf data query when state inspection is needed.
  5. Surface decisions back to the user — when a step requires a choice that materially affects scope or risk, ask using the platform's blocking question tool rather than guessing.
  • Salesforce knowledge: docs/solutions/ (search via the sf-learnings-researcher agent).
  • Plugin conventions: see CLAUDE.md for frontmatter, naming, and protected-artifact rules.
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. 7d ago First seen · 37 lines · 35 tokens per session scan A 38d5d66e2421

Subscribe to this mod's changes

sf-session-extract is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 464 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to sf-release-notes, differing in 13 lines, and is treated as a copy.

Debugging
Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens