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 field-service-to-cash-protocolgit 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/field-service-to-cash-protocol)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/field-service-to-cash-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/field-service-to-cash-protocol/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/field-service-to-cash-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/field-service-to-cash-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00133 | $0.01558 |
| Opus 5 | $0.00067 | $0.00779 |
| Sonnet 5 | $0.00027 | $0.00312 |
| Haiku 4.5 | $0.00013 | $0.00156 |
Grade A, and why
field-service-to-cash-protocol 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Field Service to Cash Protocol
Purpose
This skill orchestrates the field service to cash process (referred to as "service to deliver" in the Microsoft Dynamics 365 business process catalog) in Dynamics 365 environments. It coordinates Dynamics 365 Field Service (work order management, scheduling, service delivery, and inventory consumption) with Dynamics 365 Finance (invoicing, accounts receivable, and cash application). The protocol ensures that service is verified as delivered before invoicing, that parts consumed are accurately recorded against inventory, and that revenue is recognized in the correct period. It does not give field service configuration or financial accounting advice; all recommendations are subject to human owner confirmation.
When to use
- A field service work order must progress from creation through scheduling, delivery, parts consumption, invoicing, and payment.
- Inventory consumed during field service must be reconciled with accounts in Dynamics 365 Finance.
- A service agreement with recurring invoicing requires coordination between Field Service and Finance.
- A work order completion must be verified before an invoice is generated or posted.
- A cross-module discrepancy between field service actuals and financial postings needs investigation.
When NOT to use
- The matter is confined entirely to work order scheduling with no financial impact — route to the Field Service specialist.
- The matter involves project-based billing from Dynamics 365 Project Operations — use the appropriate project-to-profit process.
- The matter is a warranty claim or service contract renewal without an active work order — escalate to the Field Service and finance owners.
- Direct Field Service or Finance configuration is required — route to the relevant specialist agent.
Participating agents
- d365-field-service-to-cash-agent — owns work order creation, scheduling, service delivery confirmation, and inventory consumption in Dynamics 365 Field Service
- d365-finance-close-to-report-agent — owns invoicing, accounts receivable, revenue recognition, and cash application in Dynamics 365 Finance
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.
- 8d ago First seen · 100 lines · 133 tokens per session scan A 2195504fe6f4
field-service-to-cash-protocol is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed today), licensed Apache-2.0. It adds 133 tokens to every session and 1,558 once invoked, about $0.0007 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-09-04.
Other skills, from other repositories
financial-planner
Your Personal Finance Manager for Canadians — an AI financial planning partner that conducts thorough financial interviews, builds complete plans, generates interactive dashboards, and provides ongoing coaching. Use this skill whenever someone asks about budgeting, saving, investing, debt strategy, retirement…
FinOps Practice Lead
Operates the FinOps practice end-to-end -- cadences, policies, maturity assessment, and the integration with allied disciplines (ITAM, ITSM, ITFM/TBM, Security, Sustainability). Runs the discipline that aligns Engineering, Finance, and Leadership.
FinOps Intersections Coordinator
Coordinates FinOps activities with the Allied Personas -- ITAM, ITSM, ITFM/TBM, Security, and Sustainability. Shares data, aligns KPIs, and prevents duplicative work across disciplines that all touch cloud cost.
FinOps Tooling Evaluator
Build-vs-buy analysis, vendor selection, and tool-portfolio hygiene for FinOps platforms, k8s cost tools, commitment optimizers, and reporting/BI layers. Picks tools that deliver FinOps Capabilities, not logos.
FinOps Governance Lead
Operates the cross-functional FinOps practice -- policies, reviews, stakeholder alignment, and the connective tissue between engineering, finance, and leadership.
adp-workforce
ADP Workforce Now integration. Manage Persons, Organizations, Jobs, Payrolls, Benefitses, Talents. Use when the user wants to interact with ADP Workforce Now data.