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 instructions/mitkox/background-coding-agents/agents-mdgit clone --depth 1 https://github.com/mitkox/background-coding-agentsWhat 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.03014 | $0.03014 |
| Opus 5 | $0.01507 | $0.01507 |
| Sonnet 5 | $0.00603 | $0.00603 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
background-coding-agents AGENTS.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 2d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Coding Agents when working with code in this repository.
Project Overview
This is a demonstration repository showing how to apply Spotify's background coding agent concepts to industrial manufacturing environments. It's based on Spotify's 3-part engineering blog series on their journey merging 1,500+ AI-generated PRs with 60-90% time savings.
The codebase demonstrates automated PLC/SCADA code transformations across multiple manufacturing sites with safety-critical verification layers.
Key Commands
Setup
# Initial setup
./setup.sh
# Manual setup
python3 -m venv venv
source venv/bin/activate # or . venv/Scripts/activate on Windows
pip install -r requirements.txt
Running the Fleet Manager
# From root directory (using installed entry point)
fleet-manager --help
# Example: Dry-run migration
fleet-manager safety_interlock_update --dry-run
# Example: List configured sites
fleet-manager list-sites
# View migration status
fleet-manager status
Development
# Run tests (if implemented)
pytest
# Format code
black .
# Type checking
mypy agents/ verifiers/ fleet-manager/
Architecture Overview
This project implements a Fleet Management Architecture for automated code changes across manufacturing sites, analogous to Spotify's repository fleet management:
Core Components
-
Fleet Manager (
fleet-manager/cli.py)- Orchestrates migrations across multiple sites
- Targets sites based on filters (PLC type, firmware version, etc.)
- Manages verification loops and change requests
- Configuration in
fleet-manager/config.yaml
-
Background Coding Agent (
src/background_coding_agents/agents/plc_agent.py)- Transforms PLC code based on natural language prompts
- Uses iterative change-verify loops (max 10 turns)
- Supports local LLMs (vLLM, llama.cpp) for air-gapped deployments
- Cloud LLMs optional (Anthropic, OpenAI, MiniMax)
- Limited tool access (verify, git diff, ripgrep)
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.
- 2d ago First seen · 342 lines · 3,014 tokens per session scan A 97fa368a0f1b
background-coding-agents AGENTS.md is an instructions file published in the GitHub repository mitkox/background-coding-agents (22 stars, last pushed 8mo ago), licensed MIT. It adds 3,014 tokens to every session, about $0.0151 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-30.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.