agentmods.dev

orchestrate-build

orchestrate-build is a skill for Claude Code, Codex from Justinmendezai/The-Adam-Repo. It costs 94 tokens per session (3,038 once invoked), scanned A, original, Apache-2.0.

A build coordinator that follows dependencies between smaller work items, called slices, and assigns newly unblocked slices to their managers. It then runs each slice's checks itself and updates the project's status file.

In plain words
What is it for?
Use it to dispatch slice managers, start the next available batch of work, rerun verifiers, update slice statuses, and continue through later dependency waves.
Why use it?
Large builds become difficult to coordinate when one task depends on another and workers report their own progress. This keeps the dependency order and verifies completed work independently.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

not rated 12repo +1 18d ago A scan SkillSpector: warn 94 tokens original Apache-2.0

Good fit Use it to dispatch slice managers, start the next available batch of work, rerun verifiers, update slice statuses, and continue through later dependency waves.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/justinmendezai/the-adam-repo/orchestrate-build
View source ↗ Justinmendezai/The-Adam-Repo justinmendez.ai
Install

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.

Any agent
npx skills add Justinmendezai/The-Adam-Repo --skill orchestrate-build
Clone the repo
git clone --depth 1 https://github.com/Justinmendezai/The-Adam-Repo

Made for: Claude Code, Codex.

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 orchestrate-build

README.md
[![agentmods](https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/orchestrate-build/github.svg)](https://agentmods.dev/skills/justinmendezai/the-adam-repo/orchestrate-build)
Your own site
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/orchestrate-build"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/orchestrate-build/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.

agentmods 80×15 button for orchestrate-build

Your own site · 80×15
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/orchestrate-build"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/orchestrate-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,038 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 96
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium MCP Rug Pull · line 155
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.00094 $0.03038
Opus 5 $0.00047 $0.01519
Sonnet 5 $0.00019 $0.00608
Haiku 4.5 $0.00009 $0.00304

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

Security

Grade A, and why

orchestrate-build scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| scaffold | dev-launch fixups, env wiring | `bash scripts/dev-up.sh && curl -fsS localhost:3000` |
skills/orchestrate-build/SKILL.md · 203 lines

How it starts

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

orchestrate-build

The Tier-1 orchestrator loop. Permanently lean: it never reads a slice SPEC.md body, never writes product code, never trusts a worker's self-report. It walks the dependency graph in agent-control/slice-status.md, hands paths (not contents) down to per-slice managers, then re-runs each slice's verifier itself before flipping a status row.

The invariant

Information flows down as file paths, not file contents. The orchestrator passes a slice id and a list of paths to its manager. Each lower tier reads what it needs by path. Nobody pastes a 400-line spec into a prompt.

Topology

Tier 1 — orchestrate-build (this skill, you)
  holds: dep graph + 1-line statuses (agent-control/slice-status.md)
  does:  dispatch managers, re-run verifiers, flip statuses
        |
        | slice id + paths only
        v
Tier 2 — dispatch-manager (per slice, disposable)
  holds: ONE slice SPEC.md
  does:  build worker prompt, dispatch worker, return one-line summary
        |
        | scoped prompt
        v
Tier 3 — worker (composer-2-fast, best-of-n-runner)
  holds: ONE SPEC + in-scope files
  does:  write code, commit, emit <adam>COMPLETE</adam>

Fallback path: when topology_depth: 2 is set in adam.json, the orchestrator dispatches workers directly via dispatch-builder / dispatch-parallel and skips the manager hop.

Preconditions

Before running this skill:

  • slice-to-tasks has produced slices/<id>/SPEC.md + slices/<id>/verify.sh (or an inline verify one-liner in SPEC.md) for every slice.
  • tests-first has populated slices/<id>/tests/ with red tests.
  • agent-control/slice-status.md exists (created by setup-adam, one row per slice).
  • agent-control/human-queue.md exists (seeded by adam-foundation-sync) for batched operator items.
  • adam.json has topology_depth (default 3) and verifier_convention (default slices/<id>/verify.sh).

Read the full file on GitHub · 203 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. 12d ago First seen · 203 lines · 94 tokens per session scan A 45b6cd2a9f0f

Subscribe to this mod's changes

orchestrate-build is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 94 tokens to every session and 3,038 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management
Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens