Borrowing it
Nothing to install: this file belongs to fotoetienne/gru. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fotoetienne/gru/main/.claude/skills/github-issues/SKILL.mdgit clone --depth 1 https://github.com/fotoetienne/gruWrote 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/fotoetienne/gru/github-issues)<a href="https://agentmods.dev/skills/fotoetienne/gru/github-issues"><img src="https://agentmods.dev/badge/skills/fotoetienne/gru/github-issues/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/fotoetienne/gru/github-issues"><img src="https://agentmods.dev/badge/skills/fotoetienne/gru/github-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00062 | $0.01497 |
| Opus 5.5 | $0.00025 | $0.00599 |
| Sonnet 5.5 | $0.00012 | $0.00299 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
github-issues 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 2mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at managing GitHub issues for the Gru project. Follow these conventions exactly.
Creating Issues
Use gh issue create with a heredoc body:
gh issue create --title "Clear, specific title" --body "$(cat <<'EOF'
## Description
What this issue addresses.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
**Blocked by:** #X, #Y
EOF
)"
- Keep titles concise and actionable
- Include acceptance criteria when possible
- Add
**Blocked by:** #X, #Yin the body if the issue has dependencies (see Dependencies below) - Add labels with
--label "gru:todo"or other appropriate labels
Dependencies (CRITICAL)
Gru uses a two-layer dependency system. Always set dependencies both ways:
Layer 1: Body text (ALWAYS do this — works everywhere including GHES)
Include **Blocked by:** #X, #Y in the issue body. This must be:
- On a single line (only the first line after the marker is parsed)
- Using
#prefix for issue numbers (bare numbers are ignored) - Same-repo only (cross-repo references like
owner/repo#123are skipped)
When editing an existing issue to add blockers, prepend the line to the body:
# Get current body, prepend blocked-by line
CURRENT_BODY=$(gh issue view 123 --json body --jq .body)
gh issue edit 123 --body "**Blocked by:** #10, #20
$CURRENT_BODY"
Layer 2: Native GitHub Dependencies REST API (always attempt after body text)
The native API requires the blocker's internal id (not the issue number):
# 1. Get the internal id of the blocking issue
BLOCKER_ID=$(gh api /repos/OWNER/REPO/issues/BLOCKER_NUMBER --jq .id)
# 2. Set the dependency: BLOCKED_ISSUE is blocked by BLOCKER
gh api /repos/OWNER/REPO/issues/BLOCKED_NUMBER/dependencies/blocked_by \
-f issue_id="$BLOCKER_ID"
Error handling for native API
After each gh api POST, check the exit status:
- 404 / "Not Found": GHES without native dependency support — log a warning and continue. Body-text
**Blocked by:**is the universal fallback. - Other errors (422, 500, etc.): Surface the error to the user so dependency setting doesn't silently fail.
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.
- 2mo ago First seen · 175 lines · 62 tokens per session scan A 2f95108eef47
github-issues is a skill published in the GitHub repository fotoetienne/gru (11 stars, last pushed 27d ago), licensed Apache-2.0. It adds 62 tokens to every session and 1,497 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
coordinator
Take over as coordinator of the current LangWatch drive: read the live state from disk (the lane roster, the newest handover, the shape counters), report it, then work the handover's next action by writing manifests and spawning lanes. Replaces pasting a brief out of a handover document - the state is read, never…
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
company-mirror
Run a PenguinHarness organization that mirrors a real company — one digital twin per real colleague, each twin's desk bound to that colleague's chat bot, twins answering what the handbook already knows and relaying the rest to one another instead of hiring, scheduling and filing tickets.