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 agentmods add rules/gosha70/code-copilot-team/auto-build-loopgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWhat 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 | $0.00043 | $0.03623 |
| Opus 5 | $0.00022 | $0.01811 |
| Sonnet 5 | $0.00009 | $0.00725 |
| Haiku 4.5 | $0.00004 | $0.00362 |
Grade A, and why
auto-build-loop 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 yesterday.
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 — 240 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.
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.
- yesterday First seen · 240 lines · 43 tokens per session scan A e61843db4eb6
auto-build-loop is a cursor rule published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 3,623 once invoked, about $0.0002 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-08-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.