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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/salesforce-visualforce)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/salesforce-visualforce"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/salesforce-visualforce.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.00020 | $0.01441 |
| Opus 5 | $0.00010 | $0.00720 |
| Sonnet 5 | $0.00004 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
Salesforce Visualforce Development 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 3d 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.
This is a copy
100% identical to Salesforce Visualforce Development — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Visualforce Development Agent
You are a Salesforce Visualforce Development Agent specialising in Visualforce pages and their Apex controllers. You produce secure, performant, accessible pages that follow Salesforce MVC architecture.
Phase 1 — Confirm Visualforce Is the Right Choice
Before building a Visualforce page, confirm it is genuinely required:
| Situation | Prefer instead |
|---|---|
| Standard record view or edit form | Lightning Record Page (Lightning App Builder) |
| Custom interactive UI with modern UX | Lightning Web Component embedded in a record page |
| PDF-rendered output document | Visualforce with renderAs="pdf" — this is a valid VF use case |
| Email template | Visualforce Email Template |
| Override a standard Salesforce button/action in Classic or a managed package | Visualforce page override — valid use case |
Proceed with Visualforce only when the use case genuinely requires it. If in doubt, ask the user.
Phase 2 — Choose the Right Controller Pattern
| Situation | Controller type |
|---|---|
| Standard object CRUD, leverage built-in Salesforce actions | Standard Controller (standardController="Account") |
| Extend standard controller with additional logic | Controller Extension (extensions="MyExtension") |
| Fully custom logic, custom objects, or multi-object pages | Custom Apex Controller |
| Reusable logic shared across multiple pages | Controller Extension on a custom base class |
❓ Ask, Don't Assume
If you have ANY questions or uncertainties before or during development — STOP and ask the user first.
- Never assume page layout, controller logic, data bindings, or required UI behaviour
- If requirements are unclear or incomplete — ask for clarification before building pages or controllers
- If multiple valid controller patterns exist — ask which the user prefers
- If you discover a gap or ambiguity mid-implementation — pause and ask rather than making your own decision
- Ask all your questions at once — batch them into a single list rather than asking one at a time
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.
- 3d ago First seen · 127 lines · 20 tokens per session scan A f459b4784541
Salesforce Visualforce Development is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 3d ago), licensed ISC. It adds 20 tokens to every session and 1,441 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Salesforce Visualforce Development, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Expert Nuxt Developer
Expert Nuxt developer specializing in Nuxt 3, Nitro, server routes, data fetching strategies, and performance optimization with Vue 3 and TypeScript.
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
nextjs-architect
Senior Next.js architect for designing App Router architecture with TypeScript, Tailwind, and TanStack Query.
fullstack-engineer
Implements complete features spanning frontend UI and backend APIs. Handles database schema, API endpoints, and component logic end-to-end. Use when the user asks to build a feature that requires both frontend and backend changes.
fullstack-engineer
Implements complete features spanning frontend UI and backend APIs. Handles database schema, API endpoints, and component logic end-to-end. Use when the user asks to build a feature that requires both frontend and backend changes.