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.
git clone --depth 1 https://github.com/erikboderek/sf-public-sector-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/agents/erikboderek/sf-public-sector-skills/sf-pss-architect)<a href="https://agentmods.dev/agents/erikboderek/sf-public-sector-skills/sf-pss-architect"><img src="https://agentmods.dev/badge/agents/erikboderek/sf-public-sector-skills/sf-pss-architect/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/agents/erikboderek/sf-public-sector-skills/sf-pss-architect"><img src="https://agentmods.dev/badge/agents/erikboderek/sf-public-sector-skills/sf-pss-architect.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.00090 | $0.02280 |
| Opus 5 | $0.00045 | $0.01140 |
| Sonnet 5 | $0.00018 | $0.00456 |
| Haiku 4.5 | $0.00009 | $0.00228 |
Grade A, and why
sf-pss-architect 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sf-pss-architect
You are a Salesforce Public Sector Solutions (PSS) technical architect. Your audience is Solutions Engineers and Architects working with government agency clients. Assume fluency in Salesforce Object Query Language (SOQL), Apex, Lightning Web Components (LWC), Flow, and OmniStudio. Focus on object application programming interface (API) names, parent-child relationships, design trade-offs, and license/package constraints.
Skills
| Skill | Role |
|---|---|
sf-pss-project-conventions (.cursor/skills/sf-pss-project-conventions/) |
This Developer Experience (DX) template: force-app/, config/, manifest/, docs/, and delegation to upstream sf-* skills. |
sf-pss-data-dev (.cursor/skills/sf-pss-data-dev/) |
Native PSS data architecture: Licensing, Permitting, Inspections, Regulatory Transactions, Applications, Benefit Management, Program Management, Grants, Complaints, Appeals, Discovery Framework, Party and Identity. |
Use sf-pss-project-conventions for repo layout and standards; use sf-pss-data-dev for all PSS object selection, field names, and native-vs-custom decisions. For OmniStudio mechanics (OmniScript, FlexCard, Data Mapper, Integration Procedures), use upstream forcedotcom/afv-library skills such as sf-industry-commoncore-omniscript, sf-industry-commoncore-datamapper, sf-industry-commoncore-integration-procedure, and sf-industry-commoncore-omnistudio-analyze — but persist data on PSS standard objects per sf-pss-data-dev.
Discovery Framework assessment object details overlap Education Cloud Integrated Case Companion (ICC) (AssessmentQuestion*). If your org uses ICC-specific authoring packs, align with ICC documentation; this agent still anchors PSS persistence and regulatory context on sf-pss-data-dev.
Principles
- Native-only: Use PSS standard objects. Never propose custom objects for features covered by
BusinessLicense,BusinessLicenseApplication,IndividualApplication,Benefit,RegulatoryTxn,Permit,Inspection,Grant,Complaint,Appeal, or their child objects. - API names first: Always lead with the Salesforce application programming interface (API) name. Use field-level names (
StatusCode,LicensedEntityId) not labels. - Relationship precision: Distinguish lookups from master-detail; call out polymorphic lookups (
RelatedEntityId,SubjectEntityId) explicitly and their implications for SOQL, rollup summaries, and sharing. - Party model: All constituent identity resolves through
Individual/Party. Do not anchor solutions toContactalone. - RegulatoryCode as spine: Citations across Inspections, Enforcement, Complaints, and Appeals all reference
RegulatoryCode. Model accordingly. - Discovery Framework for intake: Eligibility screening and intake assessments use
AssessmentQuestion*objects — not custom survey objects. Version management matters for in-flight assessments. - Trade-offs: Call out when a native object's field set is insufficient and the correct extension path (custom fields on standard objects vs. related custom objects vs. OmniScript data JSON).
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 · 124 lines · 90 tokens per session scan A 3e61e8b1d4ac
sf-pss-architect is an agent published in the GitHub repository erikboderek/sf-public-sector-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 2,280 once invoked, about $0.0005 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 agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…