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 erp-crm-cutover-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/erp-crm-cutover-protocol)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/erp-crm-cutover-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/erp-crm-cutover-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/erp-crm-cutover-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/erp-crm-cutover-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.00148 | $0.01763 |
| Opus 5 | $0.00074 | $0.00881 |
| Sonnet 5 | $0.00030 | $0.00353 |
| Haiku 4.5 | $0.00015 | $0.00176 |
Grade A, and why
erp-crm-cutover-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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ERP / CRM Cutover Protocol
Purpose
This skill defines the controlled sequence for taking a Dynamics 365 ERP or CRM implementation from pre-production readiness through mock migration, data reconciliation, runbook execution, rollback validation, and the Success by Design (SbD) go-live gate to production go-live. It exists so that no cutover proceeds without tested rollback paths, reconciled data, and explicit stakeholder sign-off at each gate. It does not execute migration scripts or production deployments; it structures the process so human owners can make well-informed go/no-go decisions.
When to use
- A Dynamics 365 Finance, Supply Chain Management, Customer Engagement, or Business Central implementation is entering the Prepare phase and a cutover plan must be validated.
- A mock cutover has been completed and reconciliation findings must be reviewed before the real cutover is authorised.
- An organisation needs to confirm SbD go-live gate criteria before requesting Microsoft FastTrack go-live readiness review.
- An existing production environment must be refreshed or migrated to a new release and cutover risk must be assessed.
When NOT to use
- The go-live has already completed and this is post-go-live hypercare support — use the hypercare support runbook instead.
- The migration involves a third-party ERP not on the Dynamics 365 platform — this protocol is scoped to Dynamics 365.
- You need live production database or environment access to execute migration scripts — that requires the infrastructure owner; this protocol is recommendation-only.
Participating agents
d365-data-migration-cutover-agent(primary — mock migration, data reconciliation, cutover runbook, rollback plan)d365-success-by-design-governance-agent(SbD gate review, go-live readiness sign-off)d365-security-sod-governance-agent(separation of duties validation, security role sign-off)
Inputs required
- Cutover plan document (task list, owners, timing, rollback steps)
- Data migration strategy and scripts (for review, not execution)
- Mock cutover results from sandbox environment (including error log)
- Go-live checklist status from the SbD Prepare phase
- Security role assignments and SoD analysis for go-live users
- Integration test results and external dependency sign-off
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 · 143 lines · 148 tokens per session scan A 995fe3401524
erp-crm-cutover-protocol is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed today), licensed Apache-2.0. It adds 148 tokens to every session and 1,763 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
r-dev
R development packages. Use for package development, testing, documentation, code style, and IDE setup.
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's instructions file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the…
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's rules file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the user…
testthat
R testthat package for unit testing. Use for writing and running unit tests for R packages.
covr
R covr package for test coverage. Use for measuring and reporting test coverage of R packages.
r-dev-testing
R testing with testthat, covr, mockery. Use for unit tests, coverage, and mocking.