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.
npx skills add skyfox675/agents-skills --skill gh-issue-lockinggit clone --depth 1 https://github.com/skyfox675/agents-skillsWrote 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.
[](https://agentmods.dev/skills/skyfox675/agents-skills/gh-issue-locking)<a href="https://agentmods.dev/skills/skyfox675/agents-skills/gh-issue-locking"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/gh-issue-locking/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.
<a href="https://agentmods.dev/skills/skyfox675/agents-skills/gh-issue-locking"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/gh-issue-locking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 92 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 230 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00187 | $0.04823 |
| Opus 5 | $0.00093 | $0.02412 |
| Sonnet 5 | $0.00037 | $0.00965 |
| Haiku 4.5 | $0.00019 | $0.00482 |
Grade A, and why
gh-issue-locking 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gh-issue-locking: Claim, Coordinate, Release
Multiple orchestrator sessions — run by different humans, on different machines, at the same time — work the same issue queue. Without a claim protocol, two agents silently pick up the same issue, burn duplicate work, and open conflicting PRs. This skill is the claim protocol: how to lock an issue before dispatching work, how to recognize and respect (or reclaim) someone else's lock, and how to release cleanly on every exit path.
Related skills: pick what to claim with the gh-issue-filing and gh-issue-labels skills; dispatch the work with the dispatching-subagents skill; run the surrounding loop with the orchestrating-slots skill; drive the resulting PR with the driving-prs-to-merge skill.
Project bindings
These values are project policy, not protocol. The adopting project defines them in its own CLAUDE.md; this skill refers to them by placeholder.
| Binding | Meaning | Proven default |
|---|---|---|
<repo-slug> |
org/repo for --repo flags (or omit when cwd is the checkout) |
— |
<integration-branch> |
Branch agent PRs merge into | dev (default branch was main) |
<claim-label> |
Repo-wide "an automation holds this" label | agent-claimed, color F0E68C — created by the gh-issue-labels bootstrap script |
<lock-marker> |
Stable greppable token in every lock comment | claude-lock: |
<hold-label> |
Operator-held "humans only, never dispatch" label | do-not-dispatch — label-name comparisons in jq filters are case-sensitive; whatever casing the bootstrap script creates is the only casing filters may assume (the bundled script creates lowercase names) |
<stale-window> |
Lock age threshold before reclaim is considered | 24h (tune to typical PR cycle time) |
<worktree-dir> |
Where agent worktrees live | see the dispatching-subagents skill |
<chat-channel> |
Team real-time channel for urgent pings | Slack |
<bot-trigger> |
The project's human-only AI-mention trigger | @claude |
| Operator logins | Informational roster of known operators | resolve dynamically — see below |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 245 lines · 187 tokens per session scan A 51db061125c8
gh-issue-locking is a skill published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 187 tokens to every session and 4,823 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.