Agent skill

Swe Af

Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software.

MITAuto-check passedDevelopment

Install Swe Af

skills CLI

$ npx skills add Agent-Field/SWE-AF --skill swe-af -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Agent-Field/SWE-AF swe-af --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Agent-Field/SWE-AF.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs .claude/skills/swe-af && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "swe-af" agent skill from https://github.com/Agent-Field/SWE-AF/tree/main/docs into .claude/skills/swe-af/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swe-af", 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

$skill-installer install https://github.com/Agent-Field/SWE-AF/tree/main/docs

Type 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.

skills CLI

$ npx skills add Agent-Field/SWE-AF --skill swe-af -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Agent-Field/SWE-AF swe-af --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Agent-Field/SWE-AF.git skills-src && mkdir -p .agents/skills && cp -r skills-src/docs .agents/skills/swe-af && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "swe-af" agent skill from https://github.com/Agent-Field/SWE-AF/tree/main/docs into .agents/skills/swe-af/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swe-af", 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.

skills CLI

$ npx skills add Agent-Field/SWE-AF --skill swe-af -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Agent-Field/SWE-AF swe-af --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Agent-Field/SWE-AF.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/docs .cursor/skills/swe-af && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "swe-af" agent skill from https://github.com/Agent-Field/SWE-AF/tree/main/docs into .cursor/skills/swe-af/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swe-af", 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

$ gemini skills install https://github.com/Agent-Field/SWE-AF.git --path docs

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Agent-Field/SWE-AF --skill swe-af -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Agent-Field/SWE-AF swe-af --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Agent-Field/SWE-AF.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/docs .gemini/skills/swe-af && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "swe-af" agent skill from https://github.com/Agent-Field/SWE-AF/tree/main/docs into .gemini/skills/swe-af/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swe-af", 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.

GitHub CLI

$ gh skill install Agent-Field/SWE-AF swe-af

Installs 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).

skills CLI

$ npx skills add Agent-Field/SWE-AF --skill swe-af -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Agent-Field/SWE-AF.git skills-src && mkdir -p .github/skills && cp -r skills-src/docs .github/skills/swe-af && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "swe-af" agent skill from https://github.com/Agent-Field/SWE-AF/tree/main/docs into .github/skills/swe-af/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swe-af", 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.

skills CLI

$ npx skills add Agent-Field/SWE-AF --skill swe-af -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Agent-Field/SWE-AF swe-af --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Agent-Field/SWE-AF.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/docs .opencode/skills/swe-af && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "swe-af" agent skill from https://github.com/Agent-Field/SWE-AF/tree/main/docs into .opencode/skills/swe-af/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swe-af", 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: swe-af
GitHub stars: 1k
Token cost: ~1.5k tokens
SKILL.md length: 431 words
Files: 4
Skills in repo: 2
Repo updated: Sep 24, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software.

Works in 3 steps: opencode CLI installed and in PATH → Model provider credentials configured in… → Model ID format matches what OpenCode…
Development work in your project
SKILL.md covers What It Does, Installation, Running and Triggering a Build, plus 7 more sections
Calls curl, pip and python; reaches github.com; needs OPENAI_API_KEY

What it does

Swe Af is an agent skill from Agent-Field/SWE-AF. Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `ARCHITECTURE.md`, `CONTRIBUTING.md` and `deployment.md`). Compatibility notes: opencode

It sits in Development. It works with OpenRouter. The repository describes itself as: Autonomous software engineering fleet of AI agents for production-grade PRs on AgentField: plan, code, test, and ship. The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/swe-af”

Requirements

Python 3
A credential in OPENAI_API_KEY
Compatibility (from SKILL.md): opencode

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

opencode CLI installed and in PATH
Model provider credentials configured in OpenCode (e.g., OPENAI_API_KEY for z.ai)
Model ID format matches what OpenCode expects

What it can do on your machine

Read from SKILL.md and the folder at commit 17d3160. 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
Shell commands in SKILL.md call:
- curl
- pip
- python
- codex
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- OPENAI_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
opencode
From compatibility in the SKILL.md frontmatter.

Context cost

Swe Af loads about 1.5k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 431 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~31
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

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 Agent-Field/SWE-AF at commit 17d3160, republished under its MIT licence (© Agent-Field). 431 words, ~1,513 tokens.

Download SKILL.mdSave it as .claude/skills/swe-af/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: swe-af
description: Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software.
compatibility: opencode
license: MIT

SWE-AF Usage Guide

Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software.

What It Does

SWE-AF creates a coordinated team of AI agents (planning, coding, review, QA, merge, verification) that execute in parallel based on DAG dependencies. Issues with no dependencies run simultaneously; dependent issues run sequentially.

Installation

bash

python3.12 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"

Running

Terminal 1 — Control Plane:

bash

af                  # starts AgentField on port 8080

Terminal 2 — Register Node:

bash

python -m swe_af    # registers the swe-planner node

Triggering a Build

With local repo:

bash

curl -X POST http://localhost:8080/api/v1/execute/async/swe-planner.build \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "goal": "Add JWT auth to all API endpoints",
      "repo_path": "/path/to/your/repo",
      "config": {
        "runtime": "open_code",
        "models": {
          "default": "zai-coding-plan/glm-5"
        }
      }
    }
  }'

With GitHub repo (clones + creates draft PR):

bash

curl -X POST http://localhost:8080/api/v1/execute/async/swe-planner.build \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "goal": "Add comprehensive test coverage",
      "repo_url": "https://github.com/user/my-project",
      "config": {
        "runtime": "open_code",
        "models": {
          "default": "zai-coding-plan/glm-5"
        }
      }
    }
  }'

Configuration

Key	Values	Description
`runtime`	`"claude_code"`, `"open_code"`, `"codex"`	AI backend to use
`models.default`	model ID string	Default model for all agents
`models.coder`	model ID string	Override for coder role
`models.qa`	model ID string	Override for QA role
`repo_path`	local path	Local workspace (new or existing)
`repo_url`	GitHub URL	Clone + draft PR workflow

Role-Specific Model Overrides

json

{
  "config": {
    "runtime": "open_code",
    "models": {
      "default": "zai-coding-plan/glm-5",
      "coder": "zai-coding-plan/glm-5",
      "qa": "zai-coding-plan/glm-5",
      "verifier": "zai-coding-plan/glm-5"
    }
  }
}

Available roles: pm, architect, tech_lead, sprint_planner, coder, qa, code_reviewer, qa_synthesizer, replan, retry_advisor, issue_writer, issue_advisor, verifier, git, merger, integration_tester

Multi-Repo Builds

SWE-AF supports coordinated work across multiple repositories in a single build. Pass config.repos as an array of repository objects, each with a repo_url (or repo_path) and a role. Single-repo builds remain backward compatible—just use repo_url or repo_path at the top level.

Complete Example: Primary App + Dependency

bash

curl -X POST http://localhost:8080/api/v1/execute/async/swe-planner.build \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "goal": "Add JWT auth across API and shared-lib",
      "config": {
        "repos": [
          {
            "repo_url": "https://github.com/org/main-app",
            "role": "primary"
          },
          {
            "repo_url": "https://github.com/org/shared-lib",
            "role": "dependency"
          }
        ],
        "runtime": "claude_code",
        "models": {
          "default": "sonnet"
        }
      }
    }
  }'

Repository roles:

primary: The main application being built. Changes here drive the build; failures block progress.
dependency: Libraries or services that may be modified to support the primary repo. Failures are captured but don't block primary build progress.

Show full SKILL.md (193 more words)Show less

Use Cases

Primary App + Shared Libraries: Coordinate changes between a web application and its shared utilities/SDK.
Monorepo Sub-Projects: Define multiple repos in a monorepo structure and orchestrate cross-package changes.
Microservices: When a feature spans an API service and a worker service, define roles to manage interdependencies.

Requirements for open_code Runtime

opencode CLI installed and in PATH
Model provider credentials configured in OpenCode (e.g., OPENAI_API_KEY for z.ai)
Model ID format matches what OpenCode expects

Requirements for codex Runtime

Codex CLI installed and in PATH.
For ChatGPT subscription auth: run codex login on the host, set SWE_CODEX_AUTH_MODE=chatgpt or auto, and leave OPENAI_API_KEY unset for the agent process.
For OpenAI API-platform billing: set SWE_CODEX_AUTH_MODE=api_key and OPENAI_API_KEY.

Monitoring

bash

# Check build status
curl http://localhost:8080/api/v1/executions/<execution_id>

Artifacts are saved to:

.artifacts/
├── plan/           # PRD, architecture, issue specs
├── execution/      # checkpoints, per-issue logs
└── verification/   # acceptance criteria results

What Happens in a Build

Planning — PM → Architect → Tech Lead → Sprint Planner (generates issue DAG)
Issue Writing — All issues written in parallel
Execution — Issues run level-by-level (parallel within levels)
- Each issue: Coder → QA + Reviewer (parallel) → Synthesizer
- Failures trigger advisor (retry/split/accept with debt/escalate)
Merge — Branches merged to integration branch
Integration Test — Full suite on merged code
Verification — Acceptance criteria checked against PRD

Key Endpoints

bash

POST /api/v1/execute/async/swe-planner.build     # Full build
POST /api/v1/execute/async/swe-planner.plan      # Plan only
POST /api/v1/execute/async/swe-planner.execute   # Execute existing plan
POST /api/v1/execute/async/swe-planner.resume_build  # Resume after crash

Files

SKILL.md and 3 other files in docs of Agent-Field/SWE-AF.

SKILL.md
ARCHITECTURE.md
CONTRIBUTING.md
deployment.md

Open the folder on GitHubat commit 17d3160

Compare with similar skills

Swe Af 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.

Swe Af compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Swe Af this skillAgent-Field/SWE-AF	1k	—	~1.5k	Automated safety check: Pass	MIT	13 days ago
Releaseunclecode/modelprint	128	—	~1.2k	Automated safety check: Pass	MIT	yesterday
Jgrepkeltokhy/jgrep	136	—	~1.1k	Automated safety check: Pass	MIT	9 days ago
Design Featurejanekbaraniewski/openusage	217	—	~1.4k	Automated safety check: Pass	MIT	3 days ago
Release Prepfinch-xu/cc-router	272	—	~1.5k	Automated safety check: Pass	MIT	yesterday
LLM Councilrohitg00/pro-workflow	2.9k	—	~1.1k	Automated safety check: Pass	None	9 days ago

Similar skills

Release
unclecode/modelprint
Ship a modelprint release the same way every time - gates, version stamp, changelog, tag, GitHub release, deploy, verify.
128 GitHub stars~1.2k tokensUpdated yesterday
DevelopmentAuto-check passed
Jgrep
keltokhy/jgrep
Filter text, records, code functions, or complete diff hunks by a plain-English description using Jev.
136 GitHub stars~1.1k tokensUpdated 9 days ago
DevelopmentAuto-check passed
Design Feature
janekbaraniewski/openusage
Design new features for OpenUsage with structured design docs and implementation tasks.
217 GitHub stars~1.4k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Release Prep
finch-xu/cc-router
cc-router 发版准备一条龙：升版本号 → 根据上一个 tag 以来的提交写 release-notes/<版本/ 的中英日三份更新内容 → 校验 → 给用户审 → 本地提交「Bump version to X.Y.Z」，停在打 tag 之前。当用户说「准备发版」「发个版」「发 6.1.0」「写发版说明 / 更新内容 / release notes」「bump 版本」时必须走本…
272 GitHub stars~1.5k tokensUpdated yesterday
DevelopmentAuto-check passed
LLM Council
rohitg00/pro-workflow
Provider-agnostic multi-LLM deliberation. An agent skill from rohitg00/pro-workflow.
2.9k GitHub stars~1.1k tokensUpdated 9 days ago
Agent WorkflowsAuto-check passed
Droid Model Setup
nikships/droidproxy
Configure any third-party model as a custom model in Factory Droid (~/.factory/settings.json): resolve specs (context window, max output tokens, reasoning efforts), write a safe config entry, set…
122 GitHub stars~2k tokensUpdated today
Agent WorkflowsAuto-check passed

Questions about Swe Af

What does Swe Af do?

Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software. Swe Af is an agent skill from Agent-Field/SWE-AF. Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software.

When should I use Swe Af?

Swe Af fits situations like: development work in your project.

How do I install Swe Af in Claude Code?

Run `npx skills add Agent-Field/SWE-AF --skill swe-af -a claude-code`. Or copy the skill folder (docs in Agent-Field/SWE-AF) into .claude/skills/swe-af in your project. Claude Code loads it when a task matches its description.

How do I install Swe Af in Codex?

Run `npx skills add Agent-Field/SWE-AF --skill swe-af -a codex`. Or copy the skill folder (docs in Agent-Field/SWE-AF) into .agents/skills/swe-af in your project. Codex loads it when a task matches its description.

Can I use Swe Af 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 Agent-Field/SWE-AF --skill swe-af -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swe-af, .gemini/skills/swe-af, .github/skills/swe-af and .opencode/skills/swe-af in your project.

What does Swe Af need to run?

Going by SKILL.md and its folder, Swe Af needs the command-line tools its instructions call (curl, pip, python and codex) and credentials named OPENAI_API_KEY. Our summary lists: Python 3; A credential in OPENAI_API_KEY. Compatibility (from SKILL.md): opencode.

Does Swe Af access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Swe Af 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 Swe Af use?

Swe Af is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Swe Af use?

About 1.5k tokens (SKILL.md is roughly 6.1k 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 Swe Af?

Skills that share tags, products or a category with Swe Af: Release (unclecode/modelprint, 128 stars), Jgrep (keltokhy/jgrep, 136 stars), Design Feature (janekbaraniewski/openusage, 217 stars) and Release Prep (finch-xu/cc-router, 272 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Swe Af?

Agent-Field (a GitHub organization) maintains it in Agent-Field/SWE-AF, which has 1,032 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 24, 2026.

Source: Agent-Field/SWE-AF on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Swe Af

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

SWE-AF Usage Guide

What It Does

Installation

Running

Triggering a Build

Configuration

Role-Specific Model Overrides

Multi-Repo Builds

Complete Example: Primary App + Dependency

Use Cases

Requirements for open_code Runtime

Requirements for codex Runtime

Monitoring

What Happens in a Build

Key Endpoints

Files

Compare with similar skills

Similar skills

Release

Jgrep

Design Feature

Release Prep

LLM Council

Droid Model Setup

More from Agent-Field/SWE-AF

Delegate Issue

Related

Questions about Swe Af