sf-ai-agentforce-grid

sf-ai-agentforce-grid is a skill for Codex from Jaganpro/sf-skills. It costs 165 tokens per session (3,240 once invoked), scanned C, original, MIT.

A guide for building and managing Agentforce Grid workbooks and worksheets in Salesforce. Agentforce Grid is a Salesforce workspace for organizing agent-related data and workflows in rows and columns.

In plain words
What is it for?
Use it to create workbooks and worksheets, design columns and cells, manage metadata and workflows, publish reusable YAML specifications, and connect to Grid through its available interfaces.
Why use it?
It helps turn an idea into a working Grid workbook and provides a repeatable specification for setting it up. It also addresses Salesforce authentication and alternative ways to access the Grid service.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

Good fit Use it to create workbooks and worksheets, design columns and cells, manage metadata and workflows, publish reusable YAML specifications, and connect to Grid through its available interfaces.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jaganpro/sf-skills/sf-ai-agentforce-grid
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 Jaganpro/sf-skills --skill sf-ai-agentforce-grid
Clone the repo
git clone --depth 1 https://github.com/Jaganpro/sf-skills

Made for: Codex.

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-ai-agentforce-grid

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jaganpro/sf-skills/sf-ai-agentforce-grid"><img src="https://agentmods.dev/badge/skills/jaganpro/sf-skills/sf-ai-agentforce-grid.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 165 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,240 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 28 Apr 2026
  • Snyk warn 28 Apr 2026
How audits are shown
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.00165 $0.03240
Opus 5 $0.00082 $0.01620
Sonnet 5 $0.00033 $0.00648
Haiku 4.5 $0.00016 $0.00324

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

Security

Grade C, and why

sf-ai-agentforce-grid scanned grade C with 2 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 11d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/grid_api_request.mjs, scripts/grid_rest_utils.mjs, scripts/grid_smoke_test.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- If the user is on Windows and a Unix installer fails, do the equivalent setup natively instead of insisting on `curl | bash`.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- If the user is on Windows and a Unix installer fails, do the equivalent setup natively instead of insisting on `curl | bash`.
skills/sf-ai-agentforce-grid/SKILL.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SF AI Agentforce Grid

Overview

This skill helps coding agents work effectively with Agentforce Grid in real Salesforce orgs. It combines Grid MCP workflow guidance, Windows-safe setup and API fallbacks, practical column-design patterns, and tested recipes for building useful worksheets quickly.

Invoke explicitly with $sf-ai-agentforce-grid or, where supported, /sf-ai-agentforce-grid.

This skill should be the default specialist whenever the user wants to go from idea to working Grid workbook quickly, especially if they need one of:

  • a working workbook or worksheet created in the org
  • a repeatable YAML spec for Grid
  • help understanding Grid API behavior in a real environment
  • a Windows-safe setup path
  • a publishable pattern others can reuse

Quick Start

  1. Confirm Salesforce auth first. Run sf org list --json and make sure the intended org is connected. If needed, run sf config set target-org <alias>.

  2. Prefer the Grid MCP path first. Use the Grid MCP for workbook, worksheet, column, cell, metadata, workflow, and URL operations whenever it is available in the current workspace.

  3. Fall back to direct Grid REST only when needed. On Windows, raw sf api request rest --body ... calls can fail because of JSON quoting behavior in PowerShell. When the MCP path is unavailable or misconfigured, use scripts/grid_api_request.mjs instead of hand-building sf api request rest commands.

  4. Read worksheet state from /worksheets/{id}/data. In Grid API v66.0, worksheet data is returned via columnData keyed by column ID. Do not assume a rows array exists. Use scripts/worksheet_to_rows.mjs when you need row-oriented output.

  5. Run a smoke test before real work when onboarding someone new. Use scripts/grid_smoke_test.mjs to verify auth, basic metadata, workbook create/delete, and direct REST fallback behavior. The script delegates authentication to Salesforce CLI instead of reading tokens into Node directly.

  6. Always leave the user with a clickable way back into Salesforce. Prefer a Grid/Lightning URL helper when available. If you do not have one, provide browser-safe record links using the workbook ID and worksheet ID: https://<instance>/lightning/r/<workbookId>/view https://<instance>/lightning/r/<worksheetId>/view

Read the full file on GitHub · 274 lines

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. 11d ago First seen · 274 lines · 165 tokens per session scan C a53674dc9fcd

Subscribe to this mod's changes

sf-ai-agentforce-grid is a skill published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 165 tokens to every session and 3,240 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens