What is engineering-workflow?

A system that sends engineering architecture questions to specialist agents covering databases, backends, infrastructure, and security, then combines their findings.

Use it for questions about storage, schemas, queries, APIs, concurrency, networking, or security architecture.

It helps organize decisions that involve several technical areas instead of treating each concern separately.

engineering-workflow — Skill for Claude Code by brody-0125

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/brody-0125/my-claude-skills

agentmods

npx agentmods add skills/brody-0125/my-claude-skills/engineering-workflow

Made for: Claude Code.

Or install engineering-workflow, the plugin that ships this one along with the rest of its 1 skill.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/brody-0125/my-claude-skills/engineering-workflow/github.svg)](https://agentmods.dev/skills/brody-0125/my-claude-skills/engineering-workflow)

Your own site

<a href="https://agentmods.dev/skills/brody-0125/my-claude-skills/engineering-workflow"><img src="https://agentmods.dev/badge/skills/brody-0125/my-claude-skills/engineering-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/brody-0125/my-claude-skills/engineering-workflow"><img src="https://agentmods.dev/badge/skills/brody-0125/my-claude-skills/engineering-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 8,696 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.

Model	Per session	Once invoked
Fable 5.1	$0.00086	$0.08696
Opus 5	$0.00043	$0.04348
Sonnet 5	$0.00017	$0.01739
Haiku 4.5	$0.00009	$0.00870

Measured 12d ago against content hash fba05a3aa88c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

engineering-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 12d 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.

plugins/engineering-workflow/skills/engineering-workflow/SKILL.md · 596 lines

How it starts

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

Engineering Workflow — Micro-Agent Orchestration System

A 3-tier micro-agent system that routes engineering architecture queries to specialized domain agents, resolves cross-domain constraints, and synthesizes unified recommendations.

Role

A 3-tier micro-agent orchestration system for engineering architecture decisions spanning four major systems: DB (Database), BE (Backend), IF (Infrastructure), and SE (Security).

Architecture Overview

                         Tier 1: Gateway Router (this SKILL.md)
                                    |
                    ┌───────────────┼───────────────┐
                    |               |               |
               Tier 2: System Orchestrators
               ┌────┐  ┌────┐  ┌────┐  ┌────┐
               │ DB │  │ BE │  │ IF │  │ SE │
               └──┬─┘  └──┬─┘  └──┬─┘  └──┬─┘
                  |        |        |        |
               Tier 3: Micro Agents (domain-specific)
               ┌─────────────────────────────┐
               │ A: Storage  D: API Design   │
               │ B: Query    E: Concurrency  │
               │ C: Schema   F: Networking   │
               │ ...         ...             │
               └─────────────────────────────┘

Core Principles

Constraint-first synthesis: Agents declare constraints; conflicts are detected and resolved before output
Deterministic fast-path: Use classify-query.sh for unambiguous queries; reserve LLM classification for edge cases
Graceful degradation: If an agent fails or times out, return partial results with clear warnings

Routing Table

System Detection

System	Keywords	Orchestrator
DB	database, storage engine, index, query optimization, schema, replication, sharding, partition, consistency model, isolation level, MVCC, WAL, B-tree, LSM, vacuum, ACID, DynamoDB, RCU, WCU, hot partition, adaptive capacity, throttling	`agents/db-orchestrator.md`
BE	backend, API design, service layer, concurrency, thread pool, connection pool, caching strategy, microservice, event-driven, CQRS, saga, domain model	`agents/be-orchestrator.md`
IF	infrastructure, deployment, container, kubernetes, CI/CD, load balancer, CDN, monitoring, observability, scaling, network topology, DNS, TLS	`agents/if-orchestrator.md`
SE	security, authentication, authorization, encryption, key management, RBAC, ABAC, OAuth, JWT, zero-trust, penetration, vulnerability, compliance	`agents/se-orchestrator.md`

Read the full file on GitHub · 596 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

12d ago First seen · 596 lines · 86 tokens per session scan A fba05a3aa88c

Subscribe to this mod's changes

engineering-workflow is a skill published in the GitHub repository brody-0125/my-claude-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 86 tokens to every session and 8,696 once invoked, about $0.0004 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.

Building agents Claude Code Planning bash claude-code-plugin jq mulit-agent-systems workflow

self-audit

Self-audit this skills repo against CLAUDE.md invariants, the artifact contract, and README/CLAUDE.md/docs sync via three parallel read-only subagents. Local meta-skill — independent of the /task: pipeline.

SpaiR/task-pipeline · 52 tokens

grill

Interrogate a plan or decision one question at a time before capture, keeping a decision-plus-rationale ledger, then route to the right capture skill.

SpaiR/task-pipeline · 33 tokens

architect

Answer build-or-adopt honestly, then design one committed architecture from your own understanding of the problem — driven by ranked quality attributes, stress-tested against the field and against change, proven by a walking skeleton, its consequences confirmed by the user, committed to ARCHITECTURE.md. A command the…

donald-ada/workinggenius · 80 tokens

designer

Settle the look before the pixels — audience and context first, then the base and the delta, taste settled by looking at real states, accessibility as the floor, one design language committed to DESIGN.md as tokens with roles. A command the user types, for work with an interface someone will see; standalone, no other…

donald-ada/workinggenius · 69 tokens

daily-working

End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension…

tms-tungnguyen3/daily_working · 98 tokens

compact

Put the compaction question to a snapshot that drifted — route what no longer constrains unfinished work, and say what moves before moving it. In flight or done; the log is appended to, never edited or trimmed.

donald-ada/workinggenius · 47 tokens