Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. 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/nick-pape/grackle/main/.claude/skills/set-parent/SKILL.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/set-parent)<a href="https://agentmods.dev/skills/nick-pape/grackle/set-parent"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/set-parent/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/nick-pape/grackle/set-parent"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/set-parent.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.00045 | $0.00480 |
| Opus 5.5 | $0.00018 | $0.00192 |
| Sonnet 5.5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
set-parent 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 1mo 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.
What it actually says
Set Parent — GitHub Sub-Issue Relationships
Manages parent/child (sub-issue) relationships between GitHub issues using the GraphQL API.
REPO_OWNER="nick-pape"
REPO_NAME="grackle"
Usage
/set-parent <child#> <parent#>— make child a sub-issue of parent/set-parent remove <child#> <parent#>— remove the sub-issue relationship
Step 1: Get Node IDs
Fetch node IDs for both issues:
gh api graphql -f query='
query($owner: String!, $name: String!, $parent: Int!, $child: Int!) {
repository(owner: $owner, name: $name) {
parent: issue(number: $parent) { id title }
child: issue(number: $child) { id title }
}
}
' -f owner="$REPO_OWNER" -f name="$REPO_NAME" -F parent=<PARENT_NUMBER> -F child=<CHILD_NUMBER>
Step 2: Mutate
Add sub-issue
gh api graphql -f query='mutation {
addSubIssue(input: {
issueId: "<PARENT_NODE_ID>",
subIssueId: "<CHILD_NODE_ID>"
}) { issue { number title } subIssue { number title } }
}'
Remove sub-issue
gh api graphql -f query='mutation {
removeSubIssue(input: {
issueId: "<PARENT_NODE_ID>",
subIssueId: "<CHILD_NODE_ID>"
}) { issue { number title } subIssue { number title } }
}'
Field names (easy to mix up):
issueId= the parentsubIssueId= the child
Step 3: Confirm
Report what was done: "Made #child a sub-issue of #parent" or "Removed #child from #parent's sub-issues."
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.
- 1mo ago First seen · 67 lines · 45 tokens per session scan A e76a9bebe1b6
set-parent is a skill published in the GitHub repository nick-pape/grackle (22 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 480 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
kanban-tasks
A task-board workflow for breaking work into cards and moving them through stages such as inbox, ready, doing, review, and done. It also includes a background service and a web interface for the board.
configure-coddy
Change Coddy's own configuration when the user asks for it: edit settings, providers, models, logging, permissions, or find, install, update, and remove MCP servers and skills. Stages UCI-style commands for config.yaml and commits only after the user confirms saving; MCP servers are entries of the mcp.json files. Load…
crossreview
Run when the user invokes /crossreview (or /crossreview:setup to choose the reviewers) or asks for a cross-review, a quorum review or a second opinion from other agents or models: fan a code review (uncommitted work, a branch, a commit range, files, a plan or a document) out to several console code agents (Claude…
rpa-init
Run when the user invokes /rpa-init or asks to onboard or warm up context on a repository. The agent studies code, reads documentation and test code, sets up the dev environment as the project expects, runs tests, and writes a short project report. No extra user brief is required.
rpa-gen-rules
Use when the user invokes /rpa-gen-rules or asks to create, refresh, audit, or synchronize project instructions such as root AGENTS.md, Cursor .cursor/rules, or Claude Code .claude/rules, especially when existing rule trees have drifted.
rpa-feat
Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build.