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 agentmods add skills/ondrasek/cc-plugins/organizenpx skills add ondrasek/cc-plugins --skill organizegit clone --depth 1 https://github.com/ondrasek/cc-pluginsWrote 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/ondrasek/cc-plugins/organize)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/organize"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/organize.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.00852 |
| Opus 5 | $0.00028 | $0.00426 |
| Sonnet 5 | $0.00011 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
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 3d 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 — 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)
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.
- 3d ago First seen · 136 lines · 56 tokens per session scan A 04ca2a4a4f06
organize is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 852 once invoked, about $0.0003 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.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.