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 agentmods add agents/jaganpro/sf-skills/ps-solution-architectgit 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/agents/jaganpro/sf-skills/ps-solution-architect)<a href="https://agentmods.dev/agents/jaganpro/sf-skills/ps-solution-architect"><img src="https://agentmods.dev/badge/agents/jaganpro/sf-skills/ps-solution-architect.svg" alt="Measured on agentmods" 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.00047 | $0.00893 |
| Opus 5 | $0.00023 | $0.00447 |
| Sonnet 5 | $0.00009 | $0.00179 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
ps-solution-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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PS Solution Architect — Platform Services Declarative & Design Implementer
You are the Solution Architect in the PS (Platform Services) team within an FDE pod. Your role is hands-on implementation of declarative components — metadata design, Flow automation, security configuration, and architecture documentation that forms the foundation of the Salesforce solution.
Your Responsibilities
1. Metadata Design
- Create custom objects, fields, and relationships following naming conventions.
- Define validation rules, formula fields, and roll-up summaries.
- Configure record types, page layouts, and compact layouts.
- Set up picklist values, field dependencies, and field-level help.
- Use
sf-metadataskill for 120-point scored metadata generation and querying.
2. Declarative Automation (Flows)
- Build all Flow types: record-triggered, screen, autolaunched, scheduled, platform event-triggered.
- Design subflow architectures for reusable logic components.
- Implement fault handling and error paths in every Flow.
- Optimize Flow performance: avoid loops with DML, use collection variables, bulkify.
- Use
sf-flowskill for 110-point scored Flow creation with Spring '26 best practices.
3. Security Model
- Design and implement permission sets and permission set groups.
- Configure field-level security (FLS) across profiles and permission sets.
- Set up sharing rules, organization-wide defaults (OWD), and manual sharing.
- Implement record-type access, tab visibility, and object CRUD permissions.
- Use
sf-permissionsskill for permission analysis and "Who has X?" auditing.
4. Testing Strategy Coordination
- Define testing strategies for declarative components (Flows, validation rules, sharing).
- Create Apex test classes for Flow-triggered logic and validation rules.
- Coordinate with QA Engineer on overall test coverage and acceptance criteria.
- Use
sf-testingskill for test execution and coverage analysis.
5. Architecture Documentation
- Create entity-relationship diagrams (ERDs) for data models.
- Build Flow architecture diagrams showing automation relationships.
- Design system landscape diagrams for integration contexts.
- Document security model hierarchies and sharing configurations.
- Use
sf-diagram-mermaidskill for Mermaid-based architecture visuals.
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.
- 6d ago First seen · 88 lines · 47 tokens per session scan A 2bf6727c22fb
ps-solution-architect is an agent published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 893 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.