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.
npx skills add Jaganpro/sf-skills --skill sf-datagit clone --depth 1 https://github.com/Jaganpro/sf-skillsWrote 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/skills/jaganpro/sf-skills/sf-data)<a href="https://agentmods.dev/skills/jaganpro/sf-skills/sf-data"><img src="https://agentmods.dev/badge/skills/jaganpro/sf-skills/sf-data.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
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.00076 | $0.01998 |
| Opus 5 | $0.00038 | $0.00999 |
| Sonnet 5 | $0.00015 | $0.00400 |
| Haiku 4.5 | $0.00008 | $0.00200 |
Grade A, and why
sf-data 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Data Operations Expert (sf-data)
Use this skill when the user needs Salesforce data work: record CRUD, bulk import/export, test data generation, cleanup scripts, or data factory patterns for validating Apex, Flow, or integration behavior.
When This Skill Owns the Task
Use sf-data when the work involves:
sf dataCLI commands- record creation, update, delete, upsert, export, or tree import/export
- realistic test data generation
- bulk data operations and cleanup
- Apex anonymous scripts for data seeding / rollback
Delegate elsewhere when the user is:
- writing SOQL only → sf-soql
- running or repairing Apex tests → sf-testing
- deploying metadata first → sf-deploy
- discovering schema / field definitions → sf-metadata
Important Mode Decision
Confirm which mode the user wants:
| Mode | Use when |
|---|---|
| Script generation | they want reusable .apex, CSV, or JSON assets without touching an org yet |
| Remote execution | they want records created / changed in a real org now |
Do not assume remote execution if the user may only want scripts.
Required Context to Gather First
Ask for or infer:
- target object(s)
- org alias, if remote execution is required
- operation type: query, create, update, delete, upsert, import, export, cleanup
- expected volume
- whether this is test data, migration data, or one-off troubleshooting data
- any parent-child relationships that must exist first
Core Operating Rules
sf-dataacts on remote org data unless the user explicitly wants local script generation.- Objects and fields must already exist before data creation.
- For automation testing, prefer 251+ records when bulk behavior matters.
- Always think about cleanup before creating large or noisy datasets.
- Never use real PII in generated test data.
- Prefer CLI-first for straightforward CRUD; use anonymous Apex when the operation truly needs server-side orchestration.
What ships with it
48 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/bulk/bulk-insert-10000.apex 12 KB
- assets/bulk/bulk-insert-200.apex 12 KB
- assets/bulk/bulk-insert-500.apex 13 KB
- assets/bulk/bulk-upsert-external-id.apex 13 KB
- assets/cleanup/delete-by-created-date.apex 16 KB
- assets/cleanup/delete-by-name.apex 13 KB
- assets/cleanup/delete-test-data.apex 17 KB
- assets/cleanup/rollback-transaction.apex 12 KB
- assets/csv/account-import.csv 1.8 KB
- assets/csv/contact-import.csv 1.9 KB
- assets/csv/custom-object-import.csv 1.1 KB
- assets/csv/opportunity-import.csv 1.6 KB
- assets/factories/account-factory.apex 5.6 KB
- assets/factories/case-factory.apex 8.1 KB
- assets/factories/contact-factory.apex 5.9 KB
- assets/factories/custom-object-factory.apex 11 KB
- assets/factories/event-factory.apex 9.6 KB
- assets/factories/hierarchy-factory.apex 16 KB
- assets/factories/lead-factory.apex 6.4 KB
- assets/factories/opportunity-factory.apex 7.3 KB
- assets/factories/task-factory.apex 8.1 KB
- assets/factories/user-factory.apex 8.8 KB
- assets/json/account-contact-tree.json 3.6 KB
- assets/json/account-opportunity-tree.json 3.3 KB
- assets/json/full-hierarchy-tree.json 5.8 KB
- assets/soql/aggregate.soql 12 KB
- assets/soql/child-to-parent.soql 9.8 KB
- assets/soql/parent-to-child.soql 8.6 KB
- assets/soql/polymorphic.soql 11 KB
- assets/soql/subquery.soql 16 KB
- CREDITS.md 3.4 KB
- hooks/scripts/soql_validator.py 11 KB runs code
- hooks/scripts/validate_data_operation.py 13 KB runs code
- README.md 4.4 KB
- references/anonymous-apex-guide.md 2.0 KB
- references/bulk-operations-guide.md 1.8 KB
- references/bulk-testing-example.md 4.9 KB
- references/cleanup-rollback-example.md 8.2 KB
- references/cleanup-rollback-guide.md 1.7 KB
- references/crud-workflow-example.md 3.9 KB
- references/governor-limits-reference.md 1.8 KB
- references/orchestration.md 6.6 KB
- references/relationship-query-examples.md 5.7 KB
- references/sf-cli-data-commands.md 2.3 KB
- references/soql-relationship-guide.md 2.0 KB
- references/test-data-best-practices.md 3.2 KB
- references/test-data-factory-usage.md 7.6 KB
- references/test-data-patterns.md 2.4 KB
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.
- 8d ago First seen · 245 lines · 76 tokens per session scan A d4b3ed9c1205
sf-data is a skill published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 1,998 once invoked, about $0.0004 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-30.
Other skills, from other repositories
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
adding-dbt-unit-test
Creates unit test YAML definitions that mock upstream model inputs and validate expected outputs. Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
Drizzle ORM Testing
Testing patterns for Drizzle ORM covering migration testing, query builder testing, transaction testing, and database integration testing with PostgreSQL, SQLite, and MySQL.