Context Mode Ops
mksglu/context-mode
Runs maintenance for the context-mode project with parallel subagents: issue triage, PR review, releases, bug fixes, announcements and branch syncing.
Repo adapter that runs the investigation step of the ForgeDock work-on pipeline on a GitHub issue and posts a FORGE:INVESTIGATOR report comment.
Install Forge Issue Investigator
$ npx skills add RapierCraftStudios/ForgeDock --skill work-on-investigate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-investigate --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/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/work-on/investigate .claude/skills/work-on-investigate && 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 "work-on-investigate" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/investigate into .claude/skills/work-on-investigate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-investigate", 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/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/investigateType 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 RapierCraftStudios/ForgeDock --skill work-on-investigate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-investigate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/work-on/investigate .agents/skills/work-on-investigate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "work-on-investigate" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/investigate into .agents/skills/work-on-investigate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-investigate", 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 RapierCraftStudios/ForgeDock --skill work-on-investigate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-investigate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/work-on/investigate .cursor/skills/work-on-investigate && 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 "work-on-investigate" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/investigate into .cursor/skills/work-on-investigate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-investigate", 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/RapierCraftStudios/ForgeDock.git --path .agents/skills/work-on/investigate--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 RapierCraftStudios/ForgeDock --skill work-on-investigate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-investigate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/work-on/investigate .gemini/skills/work-on-investigate && 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 "work-on-investigate" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/investigate into .gemini/skills/work-on-investigate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-investigate", 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 RapierCraftStudios/ForgeDock work-on-investigateInstalls 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 RapierCraftStudios/ForgeDock --skill work-on-investigate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/work-on/investigate .github/skills/work-on-investigate && 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 "work-on-investigate" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/investigate into .github/skills/work-on-investigate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-investigate", 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 RapierCraftStudios/ForgeDock --skill work-on-investigate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on-investigate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/work-on/investigate .opencode/skills/work-on-investigate && 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 "work-on-investigate" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on/investigate into .opencode/skills/work-on-investigate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on-investigate", 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
work-on-investigate- GitHub stars
- 117
- Token cost
- ~457 tokens
- SKILL.md length
- 200 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Repo adapter that runs the investigation step of the ForgeDock work-on pipeline on a GitHub issue and posts a FORGE:INVESTIGATOR report comment.
- Investigating a ForgeDock GitHub issue as part of the work-on pipeline
- SKILL.md covers Forge Repo Key Files, Investigation Rule and Continuation Rule
- Calls gh
- Posting a structured investigator report as an issue comment
What it does
This is a Forge repository adapter for the investigate step of the ForgeDock work-on pipeline. It treats `commands/work-on/investigate.md` as the authoritative workflow and overrides a few details: the default repository is RapierCraftStudios/forgedock, issue comments are read and written through `gh api`, `FORGE:*` markers are the main resume protocol, and missing workflow labels are created when needed instead of causing a failure.
When an issue concerns the Forge repo, the agent prioritizes a listed set of files, including the work-on, review-pr, quality-gate, orchestrate and milestone command files, the install scripts and the AGENTS.md, CLAUDE.md, CODEX and WORKFLOW docs. If the shared command's domain table points at irrelevant paths, this set replaces it. The output is a FORGE:INVESTIGATOR comment, best-effort label updates and a structured result. That result is an intermediate signal: control returns to the routing loop in `commands/work-on.md`, which re-reads GitHub and dispatches the next phase, so the pipeline does not stop there.
When your agent uses it
- Investigating a ForgeDock GitHub issue as part of the work-on pipeline
- Posting a structured investigator report as an issue comment
- Resuming a Forge investigation from its FORGE markers
Example prompts
- “Investigate the open ForgeDock issue about the quality gate and post the investigator report.”
- “Resume the investigation on this Forge issue from its FORGE markers.”
- “Run the investigate step for the review-pr command bug and update the labels.”
Requirements
- The GitHub CLI (`gh`) with access to the repository
- The ForgeDock commands folder, including commands/work-on/investigate.md
What it can do on your machine
Read from SKILL.md and the folder at commit 30c8e2a. 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:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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
Forge Issue Investigator loads about 457 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 200 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 RapierCraftStudios/ForgeDock at commit 30c8e2a, republished under its AGPL-3.0 licence (© RapierCraftStudios). 200 words, ~457 tokens.
Download SKILL.mdSave it as
.claude/skills/work-on-investigate/SKILL.md (or your agent's skills folder).- name
- work-on-investigate
- description
- Investigate a Forge GitHub issue from Codex and post a FORGE:INVESTIGATOR report.
Forge Repo Adapter: work-on/investigate
Use commands/work-on/investigate.md as the authoritative investigation workflow, with these Forge repo overrides:
- Default repo context is
RapierCraftStudios/forgedock. - Read/write issue comments via
gh api repos/RapierCraftStudios/forgedock/issues/{NUMBER}/comments. - Use
FORGE:*markers as the primary resume protocol. - Treat missing workflow labels as normal in this repo; create them when needed instead of failing.
Forge Repo Key Files
Prioritize these files when the issue is in the Forge repo:
commands/work-on.mdcommands/review-pr.mdcommands/quality-gate.mdcommands/orchestrate.mdcommands/milestone.mdinstall.sh,install-codex.shAGENTS.md,CLAUDE.md,docs/CODEX.md,docs/WORKFLOW.md- any changed or referenced file under
commands/,docs/,scripts/, or.agents/skills/
Investigation Rule
If the shared command’s domain table references project-specific paths that are not relevant to this repo, replace it with the Forge repo file set above and continue with the same output contract: post a <!-- FORGE:INVESTIGATOR --> comment, update labels best-effort, and return the structured investigate result.
Continuation Rule
Outputting INVESTIGATE_RESULT: does NOT terminate the pipeline. This result block is an intermediate signal for the work-on.md routing loop — not a final answer. After this subcommand completes, control returns to the routing loop in commands/work-on.md, which re-reads GitHub state and dispatches to the next phase (build, decompose, or INVALID stop). Do not treat the result block as a completion signal — the pipeline continues.
© RapierCraftStudios, AGPL-3.0. 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 .agents/skills/work-on/investigate of RapierCraftStudios/ForgeDock.
Open the folder on GitHubat commit 30c8e2a
Compare with similar skills
Forge Issue Investigator 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 |
|---|---|---|---|---|---|---|
| Forge Issue Investigator this skillRapierCraftStudios/ForgeDock | 117 | — | ~457 | Automated safety check: Pass | AGPL-3.0 | |
| Context Mode Opsmksglu/context-mode | 26k | — | ~6k | Automated safety check: Pass | Custom licence | |
| PRP Workstream OrchestratorWirasm/prp | 2.3k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Open Source Maintainernumman-ali/n-skills | 1.1k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Setup Matt Pocock Skillsywwynm/EverythingDone | 144 | 8 repos | ~1.7k | Automated safety check: Pass | GPL-3.0 | |
| Codex Issue Coordinatorowainlewis/blueprint | 412 | — | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
PRP Workstream Orchestrator
Wirasm/prp
Coordinates several PRP workstreams in isolated Git worktrees from one session, verifying proof, holding merge gates and sequencing the merges.
Open Source Maintainer
numman-ali/n-skills
End-to-end GitHub repository maintenance for open-source projects.
Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
Codex Issue Coordinator
owainlewis/blueprint
Lets one Codex thread run a batch of GitHub issues through separate worker threads, each with its own worktree, branch, tested pull request and gated merge.
Setup Matt Pocock Skills
yamcodes/arkenv
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
More from RapierCraftStudios/ForgeDock
Quality Gate
RapierCraftStudios/ForgeDock
Run a Forge-aware pre-commit quality gate from Codex. An agent skill from RapierCraftStudios/ForgeDock.
ForgeDock PR Review Adapter
RapierCraftStudios/ForgeDock
Adapts a shared pull request review flow to the ForgeDock repository, with its own change categories, shell and installer checks, and optional sub-agent fan-out.
Work On
RapierCraftStudios/ForgeDock
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
Work On Review
RapierCraftStudios/ForgeDock
Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
Related
Works with
Categories
Questions about Forge Issue Investigator
What does Forge Issue Investigator do?
Repo adapter that runs the investigation step of the ForgeDock work-on pipeline on a GitHub issue and posts a FORGE:INVESTIGATOR report comment. This is a Forge repository adapter for the investigate step of the ForgeDock work-on pipeline.md` as the authoritative workflow and overrides a few details: the default repository is RapierCraftStudios/forgedock, issue comments are read and written through `gh api`, `FORGE:*` markers are the main resume protocol, and missing workflow labels are created when needed instead of causing a failure.
When should I use Forge Issue Investigator?
Forge Issue Investigator fits situations like: investigating a ForgeDock GitHub issue as part of the work-on pipeline; posting a structured investigator report as an issue comment; resuming a Forge investigation from its FORGE markers.
How do I install Forge Issue Investigator in Claude Code?
Run `npx skills add RapierCraftStudios/ForgeDock --skill work-on-investigate -a claude-code`. Or copy the skill folder (.agents/skills/work-on/investigate in RapierCraftStudios/ForgeDock) into .claude/skills/work-on-investigate in your project. Claude Code loads it when a task matches its description.
How do I install Forge Issue Investigator in Codex?
Run `npx skills add RapierCraftStudios/ForgeDock --skill work-on-investigate -a codex`. Or copy the skill folder (.agents/skills/work-on/investigate in RapierCraftStudios/ForgeDock) into .agents/skills/work-on-investigate in your project. Codex loads it when a task matches its description.
Can I use Forge Issue Investigator 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 RapierCraftStudios/ForgeDock --skill work-on-investigate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/work-on-investigate, .gemini/skills/work-on-investigate, .github/skills/work-on-investigate and .opencode/skills/work-on-investigate in your project.
What does Forge Issue Investigator need to run?
Going by SKILL.md and its folder, Forge Issue Investigator needs the command-line tools its instructions call (gh). Our summary lists: The GitHub CLI (`gh`) with access to the repository; The ForgeDock commands folder, including commands/work-on/investigate.md.
Does Forge Issue Investigator access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Forge Issue Investigator 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 Forge Issue Investigator use?
Forge Issue Investigator is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Forge Issue Investigator use?
About 457 tokens (SKILL.md is roughly 1.8k 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 Forge Issue Investigator?
Skills that share tags, products or a category with Forge Issue Investigator: Context Mode Ops (mksglu/context-mode, 26k stars), PRP Workstream Orchestrator (Wirasm/prp, 2.3k stars), Open Source Maintainer (numman-ali/n-skills, 1.1k stars) and Setup Matt Pocock Skills (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Forge Issue Investigator?
RapierCraftStudios (a GitHub organization) maintains it in RapierCraftStudios/ForgeDock, which has 117 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.
Source: RapierCraftStudios/ForgeDock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.