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 kugamon/salesforce-isv-skills --skill sf-message-cataloggit clone --depth 1 https://github.com/kugamon/salesforce-isv-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/skills/kugamon/salesforce-isv-skills/sf-message-catalog)<a href="https://agentmods.dev/skills/kugamon/salesforce-isv-skills/sf-message-catalog"><img src="https://agentmods.dev/badge/skills/kugamon/salesforce-isv-skills/sf-message-catalog/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/kugamon/salesforce-isv-skills/sf-message-catalog"><img src="https://agentmods.dev/badge/skills/kugamon/salesforce-isv-skills/sf-message-catalog.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.00184 | $0.02306 |
| Opus 5.5 | $0.00074 | $0.00922 |
| Sonnet 5.5 | $0.00037 | $0.00461 |
| Haiku 4.5 | $0.00018 | $0.00231 |
Grade A, and why
sf-message-catalog 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 1mo 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Managed Package — Message Catalog Generator
Generate a complete, customer-facing catalog of every user-facing message in a Salesforce managed package. The output is a professional landscape .docx with color-coded severity, organized by component type.
Before You Begin
- Read the docx skill — locate and read the
docxSKILL.md in your available skills. You will generate a .docx using docx-js. - Identify the Salesforce org connector. Ask the user which connected Salesforce org to query. Look for available MCP tools matching patterns like
mcp__salesforce-*__tooling_executeormcp__Salesforce-*__tooling_execute. If multiple orgs are connected, ask the user to pick one. If only one is available, confirm it. - Identify the managed package namespace prefix. Ask the user for the namespace (e.g.,
kugo2p). This is used to filter Tooling API queries to only components belonging to that package.
Phase 1: Extract Messages from All Component Types
Query the Salesforce Tooling API for source code across five component types. For each, extract every user-facing message string along with its method/context, triggering condition, and severity.
1.1 Apex Classes and Triggers
Query all Apex classes and triggers in the namespace:
SELECT Id, Name, Body FROM ApexClass WHERE NamespacePrefix = '{namespace}'
SELECT Id, Name, Body FROM ApexTrigger WHERE NamespacePrefix = '{namespace}'
Search each body for these patterns (in priority order):
| Pattern | Severity |
|---|---|
.addError('...') |
ERROR |
ApexPages.addMessage(...) with ApexPages.Severity.ERROR |
ERROR |
ApexPages.addMessage(...) with ApexPages.Severity.WARNING |
WARNING |
ApexPages.addMessage(...) with ApexPages.Severity.INFO |
INFO |
ApexPages.addMessage(...) with ApexPages.Severity.CONFIRM |
CONFIRM |
throw new ...Exception('...') |
ERROR |
String variables assigned then passed to addError or addMessage |
Varies |
For each message found, record:
- Method: The Apex method name where the message lives
- Message: The exact string literal (preserve
{merge fields}) - Condition: The
if/ guard clause that triggers it (summarize in plain English) - Severity: ERROR, WARNING, INFO, or CONFIRM
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 220 lines · 184 tokens per session scan A 9d611231c87a
sf-message-catalog is a skill published in the GitHub repository kugamon/salesforce-isv-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 184 tokens to every session and 2,306 once invoked, about $0.0007 per session on Opus 5.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
convert
Convert files between 140+ formats using Conversion Tools. Two surfaces are available - the ctio CLI (preferred when shell access is available) and the hosted Conversion Tools MCP server (zero-install, works everywhere). Covers documents (Word, PDF, Excel, PowerPoint), data formats (JSON, CSV, XML, YAML, Parquet)…
parse-integration
Extract structured data from documents (invoices, receipts, purchase orders, bills of lading, bank statements, contracts, forms, ID documents, scans, photos of paper) with Parse by Conversion Tools, and build a production integration against its API. Covers getting an API key, defining an extraction schema, submitting…
authoring
Create or edit openEHR specification AsciiDoc sources, manifest.json spec entries, and boilerplate includes in specifications-XX repos. This skill should be used when the user asks to scaffold a new spec, add or edit a chapter, set up master.adoc, add a cross-reference or figure, or build a local HTML preview. Not for…
class-generation
Generate openEHR class documentation — class-definition tables, effective views, and UML class/package diagrams — from BMM schemas with bmm-publisher, for specifications-XX repos. This skill should be used when the user asks to regenerate or refresh class tables or diagrams, run bmm-publisher, generate class docs from…
amendment-record
Author or update amendment records in openEHR specification documents: the master00-amendmentrecord.adoc table in specifications-XX repos. This skill should be used when the user asks to add or update an amendment entry, choose the document version bump, add a CR/PR reference, mark a release boundary, or fix the…
review
Review an openEHR specification document for quality, completeness, and convention compliance in specifications-XX repos. This skill should be used when the user asks to review, lint, or quality-check an openEHR spec or chapter, validate its conventions, or run a pre-release review. Not for prose-style advice (use…