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 change-request-to-go-live-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/change-request-to-go-live-protocol)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/change-request-to-go-live-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/change-request-to-go-live-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/change-request-to-go-live-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/change-request-to-go-live-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.00147 | $0.02005 |
| Opus 5 | $0.00073 | $0.01002 |
| Sonnet 5 | $0.00029 | $0.00401 |
| Haiku 4.5 | $0.00015 | $0.00200 |
Grade A, and why
change-request-to-go-live-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Request to Go-Live Protocol
Purpose
This skill defines how a Dynamics 365 change request is taken from intake through impact assessment, fit-gap analysis, UAT sign-off, go/no-go decision, go-live execution, and hypercare, aligned to the Microsoft Success by Design framework. It applies the Success by Design gate structure — Solution Blueprint Review, Implementation Reviews, and Go-live Readiness Review — to ensure that only well-tested, stakeholder-approved solutions reach production. No agent authorizes go-live, cutover execution, or production deployments; those are human decisions by the project sponsor, release manager, and (where engaged) the Microsoft FastTrack for Dynamics 365 team.
When to use
- A new Dynamics 365 change request (feature, configuration, integration, or data migration) must be assessed for impact before development or deployment.
- A solution is approaching the Prepare phase and a go-live readiness gate review is needed.
- UAT sign-off or go/no-go criteria must be structured and tracked.
- A cutover plan must be reviewed for completeness before a go-live window.
- A hypercare plan must be confirmed and a support owner identified before go-live.
When NOT to use
- The change is a minor hotfix that does not require a full Solution Blueprint Review — use the environment-to-production-release-protocol with expedited gates.
- The implementation is not a Dynamics 365 project — this protocol is specifically aligned to the Dynamics 365 Success by Design framework.
- The go-live has already occurred and the project is in the Operate phase — escalate post-go-live issues to the hypercare support owner.
- The matter involves a regulatory or contractual commitment that requires legal review before the change can proceed — escalate to legal counsel first.
Participating agents
d365-success-by-design-governance-agent— primary: assesses Solution Blueprint Review readiness, go-live readiness checklist completion, and Success by Design gate complianced365-data-migration-cutover-agent— secondary: assesses data migration plan completeness, cutover plan, mock go-live execution, and rollback readiness
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 · 102 lines · 147 tokens per session scan A bb666e7dad35
change-request-to-go-live-protocol is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed today), licensed Apache-2.0. It adds 147 tokens to every session and 2,005 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.
rcmdcheck
R rcmdcheck package for R CMD check. Use for running R CMD check with better output.