code-copilot-team: Instructions file for Claude Code

adapters/github-copilot/.github/instructions/auto-build-loop.instructions.md

code-copilot-team auto-build-loop.instructions.md is an instructions file for Claude Code, GitHub Copilot from gosha70/code-copilot-team. It costs 3,577 tokens per session, scanned A, original, MIT.

A shell-driven workflow for building an approved software specification in phases. It can start fresh agent sessions, run tests, create commits, request reviews, check the remote branch, and pause at defined milestones.

In plain words
What is it for?
It is for autonomous or partly autonomous feature delivery, including phase builds, testing, peer review, commits, pull requests, and controlled merging.
Why use it?
It coordinates repetitive implementation and review work after approval, while keeping explicit points where people must approve or resolve problems.

Instructions file for Claude CodeGitHub Copilot

Written for Claude Code and GitHub Copilot: PreToolUse hook event, but also a Copilot instructions file. Also seen: positional $N argument.

This is gosha70/code-copilot-team's own configuration. It tells Claude Code and GitHub Copilot how to work on code-copilot-team 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 code-copilot-team configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gosha70/code-copilot-team. 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/gosha70/code-copilot-team/master/adapters/github-copilot/.github/instructions/auto-build-loop.instructions.md
Clone the repo
git clone --depth 1 https://github.com/gosha70/code-copilot-team

Made for: Claude Code, 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 code-copilot-team auto-build-loop.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/auto-build-loop.svg)](https://agentmods.dev/instructions/gosha70/code-copilot-team/auto-build-loop)
Your own site
<a href="https://agentmods.dev/instructions/gosha70/code-copilot-team/auto-build-loop"><img src="https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/auto-build-loop.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,577 This file is loaded in full into every session.
When invoked 3,577 The same file — it is already loaded in full.
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.03577 $0.03577
Opus 5 $0.01788 $0.01788
Sonnet 5 $0.00715 $0.00715
Haiku 4.5 $0.00358 $0.00358

Measured 3d ago against content hash 84c257c35ef2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

code-copilot-team auto-build-loop.instructions.md 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 3d 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.

adapters/github-copilot/.github/instructions/auto-build-loop.instructions.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auto-Build Loop (Autonomous Build After Spec Approval)

Once a feature's SDD bundle is approved, scripts/auto-build-loop.sh runs the build loop unattended. The driver lives OUTSIDE any copilot session (the phase workflow mandates a fresh session per phase): it starts headless build sessions, runs tests, commits, submits each phase to cross-provider review, re-checks origin alignment, and pauses for humans only at milestones or breakers. Design: specs/auto-build-loop/design.md.

Autonomy Profiles (explicit opt-in — no silent gate bypass)

Gate (phase-workflow step) advisory pr merge
Manual testing (6) deferred to milestone checkpoint deferred to milestone deferred to milestone
Commit gate (8) auto-commit, local only, isolated branch auto-commit auto-commit
Wait-for-approval (9) auto-advance; hard pause at milestones same same
Origin gate exit >= 2 (10) always escalate to human always escalate always escalate
Peer review (11) driver-run, gating, driver verifies PASS same same + green CI
Push / PR / merge never / never / never auto / auto / never auto / auto / gated auto

All three attended profiles — advisory, pr, and merge — are implemented. The fourth profile, unattended (#191 policy core, #193 admission), must be declared in automation.json itself (schema_version: 2, explicit caps.*, validated by scripts/validate-automation-config.sh; never via --profile/CCT_AUTOBUILD_PROFILE override) and must pass admission control before anything runs: validate-spec.sh --unattended --feature-id <id> --config <effective-config> proves a finalized specs/<id>/verification.yaml (generated by scripts/generate-verification-draft.sh, author-finalized) covers every FR-N with executable verifiers, every statement_sha recomputes clean against spec.md, governance holds (approved plan, origin gate ≤1), and test.command passes on the base ref (run in a throwaway worktree of HEAD — uncommitted and gitignored files are absent there, so commit what the suite needs, add a bootstrap step, or opt out with CCT_ADMISSION_TEST_IN_PLACE=1). A refusal is an un-admitted exit-1 preflight error naming every failing check; an admitted run executes unattended. See "Terminal outcomes" below for how its breakers dispatch.

Read the full file on GitHub · 239 lines

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. 3d ago First seen · 239 lines · 3,577 tokens per session scan A 84c257c35ef2

Subscribe to this mod's changes

code-copilot-team auto-build-loop.instructions.md is an instructions file published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It adds 3,577 tokens to every session, about $0.0179 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-03.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens