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 environment-to-production-release-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/environment-to-production-release-protocol)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/environment-to-production-release-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/environment-to-production-release-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/environment-to-production-release-protocol"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/environment-to-production-release-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.00128 | $0.01600 |
| Opus 5 | $0.00064 | $0.00800 |
| Sonnet 5 | $0.00026 | $0.00320 |
| Haiku 4.5 | $0.00013 | $0.00160 |
Grade A, and why
environment-to-production-release-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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment-to-Production Release Protocol
Purpose
This skill defines how Power Platform and Dynamics 365 solutions are packaged, validated, and promoted from development through test to production using managed solutions and Power Platform pipelines. It enforces the principle that only managed solutions reach production environments, that every deployment stage is preceded by pre-flight validation, and that a tested rollback path exists before a production deployment is approved. No agent authorizes a production deployment; that is a human decision by the environment owner or release manager.
When to use
- A solution in a development environment is ready to be promoted to test or production via a Power Platform pipeline.
- A release manager needs a structured checklist and gate review before approving a production deployment.
- A rollback plan must be confirmed and tested before a go-live window opens.
- A Copilot Studio agent or Power Automate flow packaged in a solution needs to be promoted through ALM stages.
- A deployment failed and a structured rollback or recovery must be initiated.
When NOT to use
- The solution has not been exported as a managed solution — unmanaged solutions must not be deployed to test or production.
- The pipeline has not been configured by an admin in the Power Platform admin center — ad hoc deployments bypass this protocol.
- The matter is a hotfix to an already-live production environment requiring emergency change procedures — use the change-request-to-go-live-protocol with expedited gates instead.
- The deployment targets an environment outside Power Platform (e.g., pure Azure infrastructure) — this protocol does not cover Azure DevOps pipelines for non-Power Platform workloads.
Participating agents
power-platform-alm-pipelines-agent— primary: validates solution packaging, pipeline stage configuration, dependency checks, and deployment readinesscopilot-studio-agent-governance-alm-agent— secondary: validates Copilot Studio agent configurations, topic schemas, and governance controls packaged in the solution
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 · 96 lines · 128 tokens per session scan A 013a942f472d
environment-to-production-release-protocol is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 128 tokens to every session and 1,600 once invoked, about $0.0006 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
bio-applied-testing-cicd
Write pytest tests/fixtures for bio functions and GitHub Actions CI with pytest-cov, ruff, black, mypy. Use when adding tests to a bio tool, writing conftest.py fixtures, or building tests.yml/lint.yml CI workflows.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
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…