A workflow for claiming a specific GitHub issue, which is a tracked piece of work, before starting it. It validates the issue, records the claim, adds a comment, and prepares a separate worktree.

Use it when taking responsibility for an issue by number or starting work on one.

It prevents unclear ownership and sets up an isolated copy of the code for the issue.

ghe-claim — Skill for Claude Code by Emasoft

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 Emasoft/ghe-marketplace --skill ghe-claim

Clone the repo

git clone --depth 1 https://github.com/Emasoft/ghe-marketplace

Made for: Claude Code.

Or install ghe, the plugin that ships this one along with the rest of its 10 skills, 2 commands, 10 agents, 5 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/emasoft/ghe-marketplace/ghe-claim/github.svg)](https://agentmods.dev/skills/emasoft/ghe-marketplace/ghe-claim)

Your own site

<a href="https://agentmods.dev/skills/emasoft/ghe-marketplace/ghe-claim"><img src="https://agentmods.dev/badge/skills/emasoft/ghe-marketplace/ghe-claim/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/emasoft/ghe-marketplace/ghe-claim"><img src="https://agentmods.dev/badge/skills/emasoft/ghe-marketplace/ghe-claim.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 326 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,175 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00326	$0.01175
Opus 5	$0.00163	$0.00588
Sonnet 5	$0.00065	$0.00235
Haiku 4.5	$0.00033	$0.00118

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

Security

Grade A, and why

ghe-claim scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/ghe/skills/ghe-claim/SKILL.md · 150 lines

How it starts

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

IRON LAW: User Specifications Are Sacred

THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.

Every word the user says is a specification - follow verbatim, no errors, no exceptions
Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST
Never take initiative to change specifications - your role is to implement, not to reinterpret
If you see an error in the spec, you MUST:
- Stop immediately
- Explain the potential issue clearly
- Wait for user guidance before proceeding
No silent "improvements" - what seems like an improvement to you may break the user's intent

Violation of this law invalidates all work produced.

Background Agent Boundaries

When running as a background agent, you may ONLY write to:

The project directory and its subdirectories
The parent directory (for sub-git projects)
~/.claude (for plugin/settings fixes)
/tmp

Do NOT write outside these locations.

GHE_REPORTS Rule (MANDATORY)

ALL reports MUST be posted to BOTH locations:

GitHub Issue Thread - Full report text (NOT just a link!)
GHE_REPORTS/ - Same full report text (FLAT structure, no subfolders!)

Report naming: <TIMESTAMP>_<title or description>_(<AGENT>).md Timestamp format: YYYYMMDDHHMMSSTimezone

ALL 11 agents write here: Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus

REQUIREMENTS/ is SEPARATE - permanent design documents, never deleted.

Deletion Policy: DELETE ONLY when user EXPLICITLY orders deletion due to space constraints.

Settings Awareness

Respects .claude/ghe.local.md:

enabled: If false, skip claim operation
enforcement_level: Affects phase-gate strictness
auto_worktree: If true, auto-create git worktree
serena_sync: If false, skip SERENA memory bank update

GitHub Elements Claim

Purpose: Claim a specific issue to START working on it. Modifies issue state.

Read the full file on GitHub · 150 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.

12d ago First seen · 150 lines · 326 tokens per session scan A 70705685b12a

Subscribe to this mod's changes

ghe-claim is a skill published in the GitHub repository Emasoft/ghe-marketplace (4 stars, last pushed 9mo ago), licensed MIT. It adds 326 tokens to every session and 1,175 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens