A set of administrative tools for GitHub issues, which are discussion and task pages attached to a code repository.

It is for locking or unlocking conversations, pinning or unpinning issues, and transferring issues. It also checks permissions and warns about actions that can limit discussion or change issue numbers.

It helps maintain issue visibility and access by handling actions such as locking discussions, pinning important issues, and transferring issues between repositories.

organize — Skill for Claude Code by ondrasek/cc-plugins

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 ondrasek/cc-plugins --skill organize

Clone the repo

git clone --depth 1 https://github.com/ondrasek/cc-plugins

Made for: Claude Code.

Or install github-issues, the plugin that ships this one along with the rest of its 8 skills, 1 agent.

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/ondrasek/cc-plugins/organize/github.svg)](https://agentmods.dev/skills/ondrasek/cc-plugins/organize)

Your own site

<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/organize"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/organize/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/ondrasek/cc-plugins/organize"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/organize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 852 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.00056	$0.00852
Opus 5.5	$0.00022	$0.00341
Sonnet 5.5	$0.00011	$0.00170
Haiku 4.5	$0.00006	$0.00085

Measured 1mo ago against content hash 04ca2a4a4f06, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

organize 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.

plugins/github-issues/skills/organize/SKILL.md · 136 lines

How it starts

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

Organize

Administrative issue operations that manage visibility and access.

Critical Rules

Read cross-cutting behaviors first: skills/shared/references/cross-cutting.md
Always add a comment explaining the administrative action and why
Warn before destructive actions — transfers change issue numbers, locking prevents comments
Check pin count before pinning (max 3 per repo)

Prerequisites Check

gh auth status

Capabilities

1. Lock Conversation

Prevent further comments on an issue.

Workflow:

View the issue to understand context:

gh issue view NUMBER --json number,title,state,comments

Add a comment explaining why (before locking):

gh issue comment NUMBER --body "Locking this conversation — REASON. Decision has been recorded above."

Lock with reason:

gh issue lock NUMBER --reason "resolved|off-topic|spam|too heated"

Valid lock reasons: resolved, off-topic, spam, too heated

2. Unlock Conversation

Re-enable comments on a locked issue.

gh issue unlock NUMBER
gh issue comment NUMBER --body "Unlocked conversation — REASON."

3. Pin Issue

Pin an issue to the top of the issues list for visibility.

Workflow:

Check current pins (max 3 per repo):

gh issue list --search "is:pinned" --json number,title

If already at 3 pins, ask the user which to unpin first.
Pin the issue:
```
gh issue pin NUMBER
```

Add a comment:

gh issue comment NUMBER --body "Pinned this issue for visibility — REASON."

4. Unpin Issue

Remove an issue from pinned status.

gh issue unpin NUMBER
gh issue comment NUMBER --body "Unpinned — REASON."

5. Transfer Issue

Move an issue to a different repository.

Warnings:

The issue number will change in the destination repo
Links and references to the old number may break
Labels must exist in the destination repo (they are not transferred)

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

1mo ago First seen · 136 lines · 56 tokens per session scan A 04ca2a4a4f06

Subscribe to this mod's changes

organize is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 852 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-31.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens