Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Factory-context integrate stage (end-of-run shipping) for one dedicated builder subagent dispatched by the orchestrator after the fix wave has merged, after a GREEN verdict, or after a recorded…
Install Integrate
$ npx skills add DanMcInerney/architect-loop --skill integrate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DanMcInerney/architect-loop integrate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/integrate .claude/skills/integrate && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "integrate" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/integrate into .claude/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DanMcInerney/architect-loop/tree/main/skills/integrateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DanMcInerney/architect-loop --skill integrate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DanMcInerney/architect-loop integrate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/integrate .agents/skills/integrate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "integrate" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/integrate into .agents/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DanMcInerney/architect-loop --skill integrate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DanMcInerney/architect-loop integrate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/integrate .cursor/skills/integrate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "integrate" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/integrate into .cursor/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DanMcInerney/architect-loop.git --path skills/integrate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DanMcInerney/architect-loop --skill integrate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DanMcInerney/architect-loop integrate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/integrate .gemini/skills/integrate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "integrate" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/integrate into .gemini/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DanMcInerney/architect-loop integrateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DanMcInerney/architect-loop --skill integrate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/integrate .github/skills/integrate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "integrate" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/integrate into .github/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DanMcInerney/architect-loop --skill integrate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DanMcInerney/architect-loop integrate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/integrate .opencode/skills/integrate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "integrate" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/integrate into .opencode/skills/integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
integrate- GitHub stars
- 626
- Token cost
- ~1.1k tokens
- SKILL.md length
- 605 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Factory-context integrate stage (end-of-run shipping) for one dedicated builder subagent dispatched by the orchestrator after the fix wave has merged, after a GREEN verdict, or after a recorded…
- Works in 5 steps: Confirm you are on the factory branch… → Merge remaining green job branches one… → If a conflict appears during this ship… → …
- Tasks that involve Subagents
- SKILL.md covers Scope, Grounding, Docs Pass (first step, before… and Integration, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Integrate is an agent skill from DanMcInerney/architect-loop. Factory-context integrate stage (end-of-run shipping) for one dedicated builder subagent dispatched by the orchestrator after the fix wave has merged, after a GREEN verdict, or after a recorded ruling skips the review. First step is the docs pass — update product docs from the change-context digest — then end-of-run integration, postflight, PR or markdown finish prep, and a digest DRAFT; returns evidence for the orchestrator to rule on.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Subagents. The repository describes itself as: Super optimized /goal loop. Massive token savings and higher quality. Smart model designs and reviews, cheaper model builds.. The licence is MIT.
When your agent uses it
- Tasks that involve Subagents
Example prompts
- “/integrate”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Confirm you are on the factory branch for the run.
- Merge remaining green job branches one at a time.
- If a conflict appears during this ship stage, resolve the smallest correct
- After each merge and after any conflict resolution, run postflight.
- Before returning, run the full closing verification: validator plus every
What it can do on your machine
Read from SKILL.md and the folder at commit 28dca7d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Integrate loads about 1.1k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 605 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DanMcInerney/architect-loop at commit 28dca7d, republished under its MIT licence (© DanMcInerney). 605 words, ~1,135 tokens.
Download SKILL.mdSave it as
.claude/skills/integrate/SKILL.md (or your agent's skills folder).- name
- integrate
- description
- Factory-context integrate stage (end-of-run shipping) for one dedicated builder subagent dispatched by the orchestrator after the fix wave has merged, after a GREEN verdict, or after a recorded ruling skips the review. First step is the docs pass — update product docs from the change-context digest — then end-of-run integration, postflight, PR or markdown finish prep, and a digest DRAFT; returns evidence for the orchestrator to rule on.
Integrate
You are the integrate subagent for one factory run. You may be dispatched as a Claude Agent-tool job or a codex exec job; keep the operating contract the same in either backend. The orchestrator dispatches you after the fix wave has merged, after a GREEN verdict, or after a recorded ruling skips the review.
Scope
The docs pass, then end-of-run integration. Merge any remaining green job branches into the factory branch, then run postflight. Do not accept red check-runner, review, or postflight evidence as shippable.
Resolve merge conflicts AT SHIP TIME ONLY. Mid-run conflicts remain decomposition failures: stop, report the branch and file evidence, and tell the orchestrator to re-spec the graph. When you resolve a ship-time conflict, rerun the full closing state before reporting success: validator plus every graded RUN item for the run must still be green after the resolution.
Do not implement new slice behavior. Do not edit frozen checks. Do not close issues, post tracker comments, approve your own work, or decide whether the run ships. Product docs are the one edit surface you own: the docs pass below. The orchestrator rules on your result.
Grounding
Before changing any state, collect command evidence for:
- current branch, HEAD, and remotes;
- run and tracking-issue identifiers plus the change-context digest, from your dispatch block;
- remaining green job branches to merge;
- shipped issues, skipped issues, rulings, and residual risks;
- frozen check locations and the closing validator command.
Every claim in your report must be backed by a command result. If a tool is missing or blocked, record the exact command, exit, and output.
Docs Pass (first step, before any merge)
Consume the change-context digest — shipped issues with one-liners, diffstats, rulings pointers, docs debt, domain-language changes — and bring the product docs (README, design and architecture docs, glossary) up to what actually shipped: new features and flows documented, retired behavior deleted, glossary terms current, diagrams' labels still true. Retire every docs-debt item or record why it stays. Product docs are the highest-contention files in a repo; this single pass replaces per-builder doc edits. Commit the docs pass as its own commit on the factory branch.
Show full SKILL.md (251 more words)Show less
Integration
- Confirm you are on the factory branch for the run.
- Merge remaining green job branches one at a time.
- If a conflict appears during this ship stage, resolve the smallest correct integration, then record conflicted paths, resolution summary, and commands.
- After each merge and after any conflict resolution, run postflight.
- Before returning, run the full closing verification: validator plus every graded RUN item for the run.
If any merge, postflight, validator, or graded RUN item stays red, stop and return a BLOCKED digest DRAFT with the raw evidence.
Finish Prep
Github mode:
- ensure the branch is pushed;
- prepare the PR body with
Closes #<tracking-issue>; - list shipped issues;
- include one per-issue back-link for every shipped issue;
- include skipped issues and residual risks in the digest DRAFT.
Markdown mode:
- leave the branch ready;
- append the digest DRAFT and merge instructions to the markdown finish record;
- include shipped issues, skipped issues, residual risks, and verification evidence.
The digest is a DRAFT returned to the orchestrator. It must name shipped, skipped, residual risks, and verification evidence. The orchestrator posts, approves, closes, or requests another ruling.
Glossary Contract
Use the codebase-design glossary exactly: module, interface, implementation, depth, seam, adapter, leverage, locality; run, tracking issue, issue, slice, frozen check, check-runner, strategist, builder, orchestrator, factory branch, worktree, job report, verdict, ruling, digest, hard stop.
Do not substitute component, service, boundary, or API for module or interface. Do not say task or ticket for issue. Do not say test file for frozen check.
© DanMcInerney, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/integrate of DanMcInerney/architect-loop.
Open the folder on GitHubat commit 28dca7d
Compare with similar skills
Integrate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Integrate this skillDanMcInerney/architect-loop | 626 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 38 repos | ~1.2k | Automated safety check: Pass | None | |
| Dispatching Parallel Agentsultralisp/ultralisp | 258 | 41 repos | ~1.5k | Automated safety check: Pass | None | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| Task Observerrebelytics/one-skill-to-rule-them-all | 3.2k | 1 repos | ~12k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
- Official
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Dispatching Parallel Agents
ultralisp/ultralisp
A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
More from DanMcInerney/architect-loop
All 11 skills in this repoArchitect Research
DanMcInerney/architect-loop
A skill your agent uses when the user asks for discovery-scale research that informs a decision: brainstorming a project or feature, choosing a technology, or requests like "research X", "what's the…
Adversarial Review
DanMcInerney/architect-loop
A skill your agent uses when the architect factory orchestrator dispatches a fresh strategist subagent to harden a draft spec: falsify it with file:line evidence, fold the surviving findings into a…
Architect
DanMcInerney/architect-loop
A skill your agent uses when the user asks to architect, run or continue the autonomous software factory, turn a goal into a hardened tracker issue plan, dispatch builder jobs, grade finished work…
Architect Fast
DanMcInerney/architect-loop
A skill your agent uses when the user asks to architect-fast a change, run the light factory lane, or factory-build a small goal — a few files, roughly one sitting, at most ~3 parallel issues — into…
Final Review
DanMcInerney/architect-loop
A skill your agent uses for the closing whole-run review in the architect factory — the only model review in the loop: dispatched by the orchestrator, at finish, to one fresh strategist subagent…
Frozen Checks
DanMcInerney/architect-loop
A skill your agent uses when the strategist drafts per-issue graded checks after decomposition and before builder dispatch.
Related
Categories
Questions about Integrate
What does Integrate do?
Factory-context integrate stage (end-of-run shipping) for one dedicated builder subagent dispatched by the orchestrator after the fix wave has merged, after a GREEN verdict, or after a recorded…. Integrate is an agent skill from DanMcInerney/architect-loop. Factory-context integrate stage (end-of-run shipping) for one dedicated builder subagent dispatched by the orchestrator after the fix wave has merged, after a GREEN verdict, or after a recorded ruling skips the review.
When should I use Integrate?
Integrate fits situations like: tasks that involve Subagents.
How do I install Integrate in Claude Code?
Run `npx skills add DanMcInerney/architect-loop --skill integrate -a claude-code`. Or copy the skill folder (skills/integrate in DanMcInerney/architect-loop) into .claude/skills/integrate in your project. Claude Code loads it when a task matches its description.
How do I install Integrate in Codex?
Run `npx skills add DanMcInerney/architect-loop --skill integrate -a codex`. Or copy the skill folder (skills/integrate in DanMcInerney/architect-loop) into .agents/skills/integrate in your project. Codex loads it when a task matches its description.
Can I use Integrate in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DanMcInerney/architect-loop --skill integrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integrate, .gemini/skills/integrate, .github/skills/integrate and .opencode/skills/integrate in your project.
What does Integrate need to run?
SKILL.md names no scripts, command-line tools or credentials: Integrate is instructions for the agent only.
Does Integrate access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Integrate safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Integrate use?
Integrate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Integrate use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Integrate?
Skills that share tags, products or a category with Integrate: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Integrate?
DanMcInerney (a GitHub user) maintains it in DanMcInerney/architect-loop, which has 626 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 13, 2026.
Source: DanMcInerney/architect-loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.