agentmods.dev

AKS-Lab-GitHubCopilot: Command for GitHub Copilot

.github/prompts/spec-to-code.prompt.md

spec-to-code is a command for GitHub Copilot from microsoft/AKS-Lab-GitHubCopilot. It costs 18 tokens per session (330 once invoked), scanned A, original, MIT.

A workflow that takes an existing Markdown specification and coordinates its implementation, tests, checks, and draft pull request. A specification is a written description of the requirements and acceptance criteria for a change.

In plain words
What is it for?
Use it to hand a specification to the appropriate coding agents, run project checks and evaluations, and open a draft pull request containing the requirements.
Why use it?
It prevents coding from starting without an approved specification and keeps implementation, testing, and deployment checks in a defined order.

Command for GitHub Copilot ✓ vendor

Written for GitHub Copilot: a Copilot chat mode or prompt.

This is microsoft/AKS-Lab-GitHubCopilot's own configuration. It tells GitHub Copilot how to work on AKS-Lab-GitHubCopilot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything AKS-Lab-GitHubCopilot configures →

not rated 10repo 8d ago A scan 18 tokens original MIT
View source ↗ microsoft/AKS-Lab-GitHubCopilot
About the project

ZavaShop on AKS and Azure Container Apps is a hands-on lab for delivering a multi-agent retail supply-chain application from requirements through deployment. It demonstrates a team of six GitHub Copilot custom coding agents working across specifications, application code, MCP servers, tests, infrastructure, and CI. The catalogue entries define the agents, skills, and instructions used in that workflow.

microsoft/AKS-Lab-GitHubCopilot · 10 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to microsoft/AKS-Lab-GitHubCopilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/microsoft/AKS-Lab-GitHubCopilot/main/.github/prompts/spec-to-code.prompt.md
Clone the repo
git clone --depth 1 https://github.com/microsoft/AKS-Lab-GitHubCopilot

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for spec-to-code

README.md
[![agentmods](https://agentmods.dev/badge/commands/microsoft/aks-lab-githubcopilot/spec-to-code/github.svg)](https://agentmods.dev/commands/microsoft/aks-lab-githubcopilot/spec-to-code)
Your own site
<a href="https://agentmods.dev/commands/microsoft/aks-lab-githubcopilot/spec-to-code"><img src="https://agentmods.dev/badge/commands/microsoft/aks-lab-githubcopilot/spec-to-code/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.

agentmods 80×15 button for spec-to-code

Your own site · 80×15
<a href="https://agentmods.dev/commands/microsoft/aks-lab-githubcopilot/spec-to-code"><img src="https://agentmods.dev/badge/commands/microsoft/aks-lab-githubcopilot/spec-to-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 330 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00330
Opus 5.5 $0.00007 $0.00132
Sonnet 5.5 $0.00004 $0.00066
Haiku 4.5 $0.00002 $0.00033

Measured 1mo ago against content hash e5a95521c901, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-to-code 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 1mo 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.

.github/prompts/spec-to-code.prompt.md · 34 lines

What it actually says

Workflow: Spec → Code → Tests

Inputs

A specs/<slug>.md file from requirements-analyst. If missing, refuse and ask the user to run requirements-analyst first.

Steps

  1. Read specs/<slug>.md. Echo the Affected agents checklist back to the user.
  2. For each ticked agent / MCP server, ask the user to invoke the next agent:
    • MCP changes → mcp-builder
    • Specialist agent → agent-builder
    • Orchestrator / shared / docker-compose → orchestrator-architect
  3. After all source changes, ask the user to switch to test-author. Provide the acceptance criteria from the spec as the test brief.
  4. After tests pass locally, run: 
    uv run poe check
docker compose up -d --build
ZAVA_ENDPOINT=http://localhost:8000 uv run python -m tests.evals.run_evals
docker compose down
  5. Open a draft PR with the spec quoted in the body.

Don'ts

  • Don't write any code while in this workflow mode — delegate to the specialist agents.
  • Don't proceed to the next phase if uv run poe check is red.
Changes

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.

  1. 1mo ago First seen · 34 lines · 18 tokens per session scan A e5a95521c901

Subscribe to this mod's changes

spec-to-code is a command published in the GitHub repository microsoft/AKS-Lab-GitHubCopilot (10 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 330 once invoked, about $0.0001 per session on Opus 5.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-19.

PlanningTesting
Related

spec-to-code compared with commands from other repositories

spec-to-code next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spec-to-codemicrosoft/AKS-Lab-GitHubCopilotCommand108d agoMITA18GitHub Copilot
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code