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 iblai/government-agents --skill salesforce-government-cloudgit clone --depth 1 https://github.com/iblai/government-agentsWrote 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/iblai/government-agents/salesforce-government-cloud)<a href="https://agentmods.dev/skills/iblai/government-agents/salesforce-government-cloud"><img src="https://agentmods.dev/badge/skills/iblai/government-agents/salesforce-government-cloud/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.
<a href="https://agentmods.dev/skills/iblai/government-agents/salesforce-government-cloud"><img src="https://agentmods.dev/badge/skills/iblai/government-agents/salesforce-government-cloud.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00666 |
| Opus 5 | $0.00017 | $0.00333 |
| Sonnet 5 | $0.00007 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
salesforce-government-cloud 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 12d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Government Cloud
What it is
Salesforce Government Cloud is a FedRAMP High-authorized deployment of the Salesforce CRM platform used by federal, state, and local agencies for citizen service delivery, case management, and constituent relationship management. It provides a unified view of constituent interactions across phone, web, chat, and in-person channels.
When to use this skill
- Creating a new citizen service case from an inbound request and routing it to the correct case worker
- Reading or updating the status, notes, and resolution summary on an existing case
- Looking up a constituent's contact record and full case history
- Checking SLA compliance flags for overdue cases nearing or past response/resolution deadlines
- Linking knowledge articles to cases to provide consistent resolution guidance
Credentials
This skill authenticates using variables from the OpenClaw daemon env file ~/.openclaw/.env (template: .env.example). Required variables:
SALESFORCE_GOV_INSTANCE_URL- agency Salesforce org URL (e.g.,https://agency.my.salesforce.com)SALESFORCE_GOV_CLIENT_ID- connected app consumer keySALESFORCE_GOV_CLIENT_SECRET- connected app consumer secretSALESFORCE_GOV_USERNAME- API service account usernameSALESFORCE_GOV_PASSWORD- API service account password (append security token if required)
Key operations
POST /services/oauth2/token— obtain OAuth 2.0 access token (username-password or JWT flow)GET /services/data/v60.0/sobjects/Case/{id}— retrieve a case by Salesforce record IDPOST /services/data/v60.0/sobjects/Case— create a new service casePATCH /services/data/v60.0/sobjects/Case/{id}— update case status, priority, or resolution notesGET /services/data/v60.0/query?q=SELECT...— SOQL query for cases, contacts, or entitlementsGET /services/data/v60.0/sobjects/Contact/{id}— retrieve constituent contact record
Notes
- Government Cloud orgs run in isolated FedRAMP environments; confirm your instance URL is a
.my.salesforce.comGov Cloud endpoint, not commercial. - API rate limits depend on org edition; Government Cloud typically allows 100,000 API calls per 24-hour period per org.
- Case ownership and queue assignments follow agency-specific workflow rules; do not hard-code queue IDs across deployments.
- PII in constituent records is subject to Privacy Act and agency data handling policies; log all automated reads in the audit trail.
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.
- 12d ago First seen · 40 lines · 34 tokens per session scan A fb0b18bc5996
salesforce-government-cloud is a skill published in the GitHub repository iblai/government-agents (10 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 666 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 skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.