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 ondrasek/cc-plugins --skill triagegit 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/triage)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/triage"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/triage/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/ondrasek/cc-plugins/triage"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/triage.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.00039 | $0.01197 |
| Opus 5.5 | $0.00016 | $0.00479 |
| Sonnet 5.5 | $0.00008 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
triage 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
Read-only — does not create or modify issues.
Critical Rules
- Read cross-cutting behaviors first:
skills/shared/references/cross-cutting.md - Always use
--jsonflags for structured data, then present human-readable summaries - Surface related issues when viewing any single issue — search by keywords from title/body
- Verify
ghis available before running any commands
Prerequisites Check
gh auth status
If this fails, tell the user to run gh auth login first.
Capabilities
1. List Issues
Translate natural language queries into gh issue list flags.
Query translation examples:
| User says | Command |
|---|---|
| "show my issues" | gh issue list --assignee @me --json number,title,state,labels,updatedAt |
| "list open bugs" | gh issue list --label "bug" --state open --json number,title,assignees,updatedAt |
| "what needs triage" | gh issue list --search "no:label" --state open --json number,title,createdAt,author |
| "issues updated this week" | gh issue list --search "updated:>YYYY-MM-DD" --json number,title,state,updatedAt |
| "unassigned issues" | gh issue list --search "no:assignee" --state open --json number,title,labels,createdAt |
| "issues mentioning auth" | gh issue list --search "auth" --json number,title,state,labels |
| "closed issues this month" | gh issue list --state closed --search "closed:>YYYY-MM-01" --json number,title,closedAt |
Common flags:
gh issue list \
--state open|closed|all \
--assignee @me|USERNAME \
--label "label-name" \
--search "QUERY" \
--limit 30 \
--json number,title,state,labels,assignees,createdAt,updatedAt,closedAt,author,milestone
Output format: Present as a readable table or list. Include issue number, title, state, labels, and assignee. Add relative timestamps (e.g., "3 days ago").
2. View Issue Detail
Show comprehensive issue information with context.
# Get full issue data
gh issue view NUMBER --json number,title,state,body,labels,assignees,author,createdAt,updatedAt,closedAt,comments,milestone,projectItems
# Get linked branches and PRs
gh issue develop NUMBER --list 2>/dev/null
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 · 134 lines · 39 tokens per session scan A 668ed2200d81
triage is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,197 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.
Other skills, from other repositories
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.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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…