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 VincentChuWaiChow/vanguard-frontier-agentic --skill salesforce-risk-taxonomygit clone --depth 1 https://github.com/VincentChuWaiChow/vanguard-frontier-agenticWrote 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/vincentchuwaichow/vanguard-frontier-agentic/salesforce-risk-taxonomy)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/salesforce-risk-taxonomy"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/salesforce-risk-taxonomy/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/vincentchuwaichow/vanguard-frontier-agentic/salesforce-risk-taxonomy"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/salesforce-risk-taxonomy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 84 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00000 | $0.02007 |
| Opus 5 | $0.00000 | $0.01004 |
| Sonnet 5 | $0.00000 | $0.00401 |
| Haiku 4.5 | $0.00000 | $0.00201 |
Grade A, and why
salesforce-risk-taxonomy 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 8d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Risk Taxonomy
Purpose
This skill provides the shared vocabulary for classifying Salesforce matters by type, risk tier, and escalation gate. It exists so that all Salesforce specialist agents use consistent terminology when they classify, route, hand off, and escalate matters. It does not assess compliance, give Salesforce advice, or authorize any action.
When to use
- A matter must be assigned a standardized type before routing or capsule creation.
- A risk tier must be determined for a proposed change, finding, or event.
- An escalation gate must be checked before a handoff or approval proceeds.
- Agents need shared vocabulary to avoid classification drift across sessions.
When not to use
- You need to route the matter to an agent — use
salesforce-routing-protocol. - You need a structured handoff record — use
salesforce-case-capsule. - You need to approve or refuse a live org mutation — use
salesforce-live-change-approval-protocol. - You need to respond to a live data exposure event — use
salesforce-data-exposure-escalation-protocol.
Minimum payload (required inputs)
- Description of the Salesforce matter (sanitized, no credentials or PII).
- Available context: environment type, change scope, data sensitivity.
Matter types
| Matter type | Description |
|---|---|
org-config |
Org settings, custom settings, custom metadata, sandboxes, licenses |
automation |
Flow, approval processes, validation rules, Process Builder |
| , assignment rules | |
code |
Apex, LWC, triggers, async jobs, static resources, packages |
integration |
REST/SOAP/Bulk/Streaming APIs, Platform Events |
| , CDC, MuleSoft | |
| , middleware | |
security-iam |
Permission sets, profiles, sharing rules, OWD, role hierarchy, guest users, OAuth, Shield |
data |
Data quality, data migration, data archival, retention policies, data classification |
sales-cpq |
CPQ |
| pricing, quoting, product catalog, Revenue Cloud | |
| , order management | |
service-sla |
Service Cloud |
| entitlements, SLAs, case management, omni-channel | |
experience-cloud |
Experience Cloud |
| sites, guest-user access, sharing sets, digital experiences | |
marketing-consent |
Marketing Cloud |
| , Account Engagement | |
| , consent capture, preference centers, Data Cloud | |
agentforce-ai |
Agentforce |
| configuration, Einstein | |
| features, AI grounding, autonomous actions | |
analytics-metrics |
Reports, dashboards, CRM Analytics |
| , Tableau | |
| , metric definitions | |
slack-governance |
Slack |
| integration, workspace governance, Slack-Salesforce data flows | |
industry-vertical |
Health Cloud |
| , Financial Services Cloud | |
| , Government Cloud | |
| , regulated-vertical configuration | |
architecture |
Org strategy, multi-org topology, data model design, platform limits |
compliance |
Audit requirements, BAA/DPA obligations, regulatory mapping, evidence collection |
release-deploy |
Change sets, DX packages, CI/CD pipelines, destructive changes, sandbox refresh |
live-mutation |
Any proposed change to a production org; always triggers live-change-approval-protocol |
What ships with it
1 file 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.
- 8d ago First seen · 163 lines · 0 tokens per session scan A 5a9658d97b32
salesforce-risk-taxonomy is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,007 tokens. 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-09-04.
Other skills, from other repositories
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
analyzing-azure-activity-logs-for-threats
Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity or…
m365-entra-attack
Microsoft 365 / Entra ID red-team attack chain — current 2026 reality. AADSTS code reference, user enumeration vectors (with hardening status), Smart Lockout math, Conditional Access bypass options, ROPC + SAML SSO browser flow, Burp/Playwright templates. Built from authorized red-team work where ROPC spray surfaced…
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
codex-agent-collaboration
Delegate coding tasks to Codex AI for implementation, analysis, and alternative solutions. Use when you need a second AI perspective, want to explore different approaches, or need specialized Codex capabilities for complex coding tasks.
founder-quiz
Take a behavioral self-assessment to discover where you sit on the founder mode spectrum. 15 questions that reveal your actual operating mode — not what you think you do, but what you actually do. Use for honest self-reflection.