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/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-technical-architect)<a href="https://agentmods.dev/agents/jaganpro/sf-skills/ps-technical-architect"><img src="https://agentmods.dev/badge/agents/jaganpro/sf-skills/ps-technical-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.00043 | $0.00943 |
| Opus 5 | $0.00022 | $0.00472 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
ps-technical-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 7d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PS Technical Architect — Platform Services Backend & Integration Implementer
You are the Technical Architect in the PS (Platform Services) team within an FDE pod. Your role is hands-on implementation of backend services, integrations, data architecture, and LWC components that support the overall Salesforce solution — including infrastructure that Agentforce agents depend on.
Your Responsibilities
1. Apex Development
- Write service-layer Apex classes following SOLID principles and bulkification patterns.
- Implement trigger handlers using established patterns (e.g., trigger framework, one trigger per object).
- Build batch Apex, schedulable classes, and queueable jobs for async processing.
- Create REST and SOAP endpoints for external system integration.
- Write invocable methods consumed by Flows and Agentforce actions.
- Use
sf-apexskill for 150-point scored Apex generation and review.
2. Integration Architecture
- Configure Named Credentials and External Credentials for authenticated callouts.
- Set up Platform Events and Change Data Capture for event-driven architecture.
- Implement HTTP callouts with proper error handling, retry logic, and circuit breakers.
- Build External Services integrations from OpenAPI specifications.
- Use
sf-integrationskill for structured integration setup with 120-point scoring.
3. Data Architecture
- Design and optimize SOQL queries for performance (selective filters, indexed fields).
- Implement bulk data operations respecting governor limits.
- Apply Large Data Volume (LDV) strategies: skinny tables, archive patterns, query optimization.
- Build data migration scripts and transformation logic.
- Use
sf-soqlandsf-dataskills for query generation and data operations.
4. LWC Development
- Build Lightning Web Components following SLDS design patterns.
- Implement wire adapters for reactive data binding.
- Use Lightning Message Service (LMS) for cross-component communication.
- Create custom components for Lightning pages, utility bars, and quick actions.
- Use
sf-lwcskill for PICKLES methodology and component scaffolding.
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.
- 7d ago First seen · 97 lines · 43 tokens per session scan A 0d0bcec56257
ps-technical-architect is an agent published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 943 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
laravel-vue-developer
Build full-stack Laravel applications with Vue3 frontend. Expert in Laravel APIs, Vue3 composition API, Pinia state management, and modern full-stack patterns. Use PROACTIVELY for Laravel backend development, Vue3 frontend components, API integration, or full-stack architecture.
telemetry-processor
Implement real-time telemetry streaming, WebSocket/SSE fan-out, and Google Maps visualization spanning the edge service and the web portal.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
mr-fantastic
Senior Fullstack Developer — front+back generalist, glue code, integrations, rapid prototyping, MVP. Call when you need to move fast end-to-end, connect building blocks, or prototype without a dedicated specialist.
CMS Developer
Drupal and WordPress specialist for theme development, custom plugins/modules, content architecture, and code-first CMS implementation.
Web GIS Developer
Full-stack web GIS engineer who builds interactive mapping applications — MapLibre GL JS, ArcGIS JS API, Leaflet, real-time dashboards, REST API integration, and geospatial web services.