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 agents/icoretech/airbroke/development-workflowgit clone --depth 1 https://github.com/icoretech/airbrokeWhat 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.00000 | $0.00506 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
development-workflow 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Workflow
Container First
This repo is developed through Docker Compose. Start the main services before running repository commands:
docker compose -f docker-compose.yml up -d web db
Use docker compose exec against running services for normal work:
web: app runtime, Prisma commands, linting, typechecking, production buildtest: one-shot Vitest execution against the dedicatedtestdbservice, both available through thetestprofile
Use host commands only for Docker diagnostics such as docker compose ps,
docker compose logs, or image and volume troubleshooting.
Common Commands
docker compose exec web yarn typecheck
docker compose exec web yarn biome:lint
docker compose exec web yarn react-doctor
docker compose exec web env NODE_ENV=production yarn build
docker compose exec web yarn db:generate
docker compose exec web yarn db:migrate
docker compose exec web yarn db:seed
docker compose -f docker-compose.yml --profile test run --rm test yarn test --run
Database Workflow
DATABASE_URLis required at runtime.DIRECT_URLis required for migrations when the main URL points through a pooler or proxy.- The compose stack wires
webtodband thetestprofile totestdb. Keep app commands onweband run test commands through the profile so development data and test data stay separate without a persistent watcher. - Postgres 18+ is mounted at
/var/lib/postgresql, not/var/lib/postgresql/data.
Build and Dependency Changes
- Rebuild or restart the compose services after changing
package.json,yarn.lock, Dockerfiles, or dependency-related env. - The production image uses
output: "standalone". The runtime server is assembled from.next/standalone,.next/static,public/, andprisma/. - Keep
.envaligned with.env.distand real local values before debugging runtime issues.
Make Targets
The Makefile is only a thin Docker wrapper:
make build:docker compose build --pullmake run:docker compose up ... --remove-orphansmake stop:docker compose down --remove-orphansmake resetdb: isolatedprisma migrate reset --force
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 · 63 lines · 0 tokens per session scan A 93b7ceb7ed84
development-workflow is an agent published in the GitHub repository icoretech/airbroke (222 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 506 tokens. 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 agents, from other repositories
software-engineer
Implements Accepted specs end to end, fixes bugs, and refactors without changing behaviour. Use proactively for new features once the spec is Accepted, domain/Prisma/Server Action changes, and technical approach decisions. Do not use when the request is a problem without a spec — that is product-manager.
code-reviewer
Reviews a change against this repository's layer, tenancy, security and testing contracts. Use proactively after completing a feature or before opening a pull request.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
domain-architect
Designs domain rules, invariants and pure function contracts before implementation. Use proactively for new features with non-trivial rules, ambiguous or conflicting requirements, calculations and state machines, inconsistencies between a spec and the code, or when deciding what belongs in domain versus services.
ui-ux-developer
Designs and builds product interfaces — screens, layouts, forms, sheets, tables, dashboards, empty and error states. Use proactively when creating or refining any user-facing surface, or auditing an existing one.