Context Modes
0xNyk/lacp
Structured work modes for agent sessions. An agent skill from 0xNyk/lacp.
Headless self-verification gate a Foreman worker runs before it claims an issue is done.
Install Foreman Verify
$ npx skills add VisionForge-OU/foreman --skill foreman-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VisionForge-OU/foreman foreman-verify --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/VisionForge-OU/foreman.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/foreman/skills/foreman-verify .claude/skills/foreman-verify && 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 "foreman-verify" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-verify into .claude/skills/foreman-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-verify", 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/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-verifyType 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 VisionForge-OU/foreman --skill foreman-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VisionForge-OU/foreman foreman-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/foreman/skills/foreman-verify .agents/skills/foreman-verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "foreman-verify" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-verify into .agents/skills/foreman-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-verify", 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 VisionForge-OU/foreman --skill foreman-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VisionForge-OU/foreman foreman-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/foreman/skills/foreman-verify .cursor/skills/foreman-verify && 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 "foreman-verify" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-verify into .cursor/skills/foreman-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-verify", 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/VisionForge-OU/foreman.git --path src/foreman/skills/foreman-verify--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 VisionForge-OU/foreman --skill foreman-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VisionForge-OU/foreman foreman-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/foreman/skills/foreman-verify .gemini/skills/foreman-verify && 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 "foreman-verify" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-verify into .gemini/skills/foreman-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-verify", 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 VisionForge-OU/foreman foreman-verifyInstalls 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 VisionForge-OU/foreman --skill foreman-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/foreman/skills/foreman-verify .github/skills/foreman-verify && 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 "foreman-verify" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-verify into .github/skills/foreman-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-verify", 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 VisionForge-OU/foreman --skill foreman-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VisionForge-OU/foreman foreman-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/foreman/skills/foreman-verify .opencode/skills/foreman-verify && 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 "foreman-verify" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-verify into .opencode/skills/foreman-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-verify", 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
foreman-verify- GitHub stars
- 444
- Token cost
- ~901 tokens
- SKILL.md length
- 472 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Headless self-verification gate a Foreman worker runs before it claims an issue is done.
- Works in 5 steps: Identify the exact command that proves it. → Run it fresh and in full — the full… → Read the whole output: exit status,… → …
- Tasks that involve Verification before completion
- SKILL.md covers The Iron Law, The gate function, What counts (and what doesn't) and Output, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Foreman Verify is an agent skill from VisionForge-OU/foreman. Headless self-verification gate a Foreman worker runs before it claims an issue is done. Re-run the real commands, read the actual output, and only then write the FOREMAN-SUMMARY — evidence before claims, always. Used inside a foreman-tdd build session; emits no summary of its own.
Its SKILL.md is about 900 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 Testing & QA, covering Verification before completion and Test-driven development. The repository describes itself as: A Boris-style agentic orchestrator TUI that supervises headless Claude Code agents through a gated software-delivery pipeline — pointed at any repository.
When your agent uses it
- Tasks that involve Verification before completion
- Tasks that involve Test-driven development
Example prompts
- “/foreman-verify”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify the exact command that proves it.
- Run it fresh and in full — the full foreman-test suite (not just --fast),
- Read the whole output: exit status, failure count, the ERROR lines.
- Save the output as an evidence artifact under the run's evidence directory
- Reconcile the claim with the output. If it does not pass, the honest result is
What it can do on your machine
Read from SKILL.md and the folder at commit 92d7f79. 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
Foreman Verify loads about 901 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 472 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 472 words (~901 tokens).
“(Adapted from obra/superpowers verification-before-completion (MIT) — see NOTICE. Made headless and wired to Foreman's trust boundary: the "claim" you are gating is the foreman-tdd FOREMAN-SUMMARY block and its evidence array, and the verification commands are the project's own, run through…”
- name
- foreman-verify
- foreman_skill_version
- 1
Files
Just SKILL.md in src/foreman/skills/foreman-verify of VisionForge-OU/foreman.
Open the folder on GitHubat commit 92d7f79
Compare with similar skills
Foreman Verify 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 |
|---|---|---|---|---|---|---|
| Foreman Verify this skillVisionForge-OU/foreman | 444 | — | ~901 | Automated safety check: Pass | Custom licence | |
| Context Modes0xNyk/lacp | 305 | — | ~313 | Automated safety check: Pass | MIT | |
| Verification Before Completionforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Inline Plan ExecutionjnMetaCode/superpowers-zh | 8.3k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Conductor Workflow Patternswshobson/agents | 40k | 8 repos | ~426 | Automated safety check: Pass | MIT | |
| Vibe ImplementidiotLeoLYJ/Daliu-Awesome-Skills | 139 | — | ~2.7k | Automated safety check: Pass | None |
Similar skills
Verification Before Completion
foryourhealth111-pixel/Vibe-Skills
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.
Inline Plan Execution
jnMetaCode/superpowers-zh
Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.
Conductor Workflow Patterns
wshobson/agents
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the…
Vibe Implement
idiotLeoLYJ/Daliu-Awesome-Skills
Vibe Coding 流水线的实现阶段(流水线终点,顺序 idea → interaction → architecture → design → prototype → implement)。当 interaction.md、architecture.md、design.md、prototypes/ 已就绪,用户说"开始实现""写代码""把设计落地""进入开发""implement /…
Superpowers
Peiiii/nextclaw
A skill your agent uses when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or…
More from VisionForge-OU/foreman
All 8 skills in this repoForeman Debug
VisionForge-OU/foreman
Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry.
Foreman Grill Docs
VisionForge-OU/foreman
Headless grilling pass that challenges an approved implementation plan against the existing codebase and domain model, then writes an ADR draft and a PRD draft into the Foreman feature directory.
Foreman To Issues
VisionForge-OU/foreman
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory.
Foreman TDD
VisionForge-OU/foreman
Stack-agnostic test-driven development loop for a single Foreman issue.
Foreman Plan
VisionForge-OU/foreman
Headless implementation-plan authoring for the Foreman planning stage.
Foreman To Prd
VisionForge-OU/foreman
PRD template and authoring rules for Foreman. An agent skill from VisionForge-OU/foreman.
Related
Categories
Questions about Foreman Verify
What does Foreman Verify do?
Headless self-verification gate a Foreman worker runs before it claims an issue is done. Foreman Verify is an agent skill from VisionForge-OU/foreman. Headless self-verification gate a Foreman worker runs before it claims an issue is done.
When should I use Foreman Verify?
Foreman Verify fits situations like: tasks that involve Verification before completion; tasks that involve Test-driven development.
How do I install Foreman Verify in Claude Code?
Run `npx skills add VisionForge-OU/foreman --skill foreman-verify -a claude-code`. Or copy the skill folder (src/foreman/skills/foreman-verify in VisionForge-OU/foreman) into .claude/skills/foreman-verify in your project. Claude Code loads it when a task matches its description.
How do I install Foreman Verify in Codex?
Run `npx skills add VisionForge-OU/foreman --skill foreman-verify -a codex`. Or copy the skill folder (src/foreman/skills/foreman-verify in VisionForge-OU/foreman) into .agents/skills/foreman-verify in your project. Codex loads it when a task matches its description.
Can I use Foreman Verify 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 VisionForge-OU/foreman --skill foreman-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/foreman-verify, .gemini/skills/foreman-verify, .github/skills/foreman-verify and .opencode/skills/foreman-verify in your project.
What does Foreman Verify need to run?
SKILL.md names no scripts, command-line tools or credentials: Foreman Verify is instructions for the agent only.
Does Foreman Verify 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 Foreman Verify 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 Foreman Verify use?
Foreman Verify has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Foreman Verify use?
About 901 tokens (SKILL.md is roughly 3.6k 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 Foreman Verify?
Skills that share tags, products or a category with Foreman Verify: Context Modes (0xNyk/lacp, 305 stars), Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Inline Plan Execution (jnMetaCode/superpowers-zh, 8.3k stars) and Conductor Workflow Patterns (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Foreman Verify?
VisionForge-OU (a GitHub organization) maintains it in VisionForge-OU/foreman, which has 444 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on June 29, 2026.
Source: VisionForge-OU/foreman on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.