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/oxidian/cc-plugins/triagenpx skills add oxidian/cc-plugins --skill triagegit clone --depth 1 https://github.com/oxidian/cc-pluginsWhat 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.00019 | $0.00600 |
| Opus 5 | $0.00010 | $0.00300 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
First, run these commands and review their output:
- Current repo:
gh repo view --json nameWithOwner --jq '.nameWithOwner'
Getting the item ID
To set project fields, you need the project item ID (not the issue number):
gh project item-list {project_number} --owner {owner} --limit 300 --format json | jq '.items[] | select(.content.number == ISSUE_NUMBER) | .id'
Setting a project field
gh project item-edit --id {item-id} --project-id {project-id} --field-id {field-id} --single-select-option-id {option-id}
Issue types
Check if an issue type is set:
gh api repos/{owner}/{repo}/issues/{number} --jq '.type.name // empty'
Set an issue type (only if not already set):
gh api -X PATCH repos/{owner}/{repo}/issues/{number} --field type=Bug
Valid types: Bug, Feature, Task
Parent issues
Find an issue's parent (for sub-issues):
gh api graphql -f query='
{
repository(owner: "{owner}", name: "{repo}") {
issue(number: ISSUE_NUMBER) {
parent {
number
title
}
}
}
}'
Get the parent's project fields (to copy them):
gh project item-list {project_number} --owner {owner} --limit 300 --format json | jq '.items[] | select(.content.number == PARENT_NUMBER)'
Milestones
Check current milestone:
gh api repos/{owner}/{repo}/issues/{number} --jq '.milestone.title // empty'
Set a milestone (use the milestone number, not title):
gh api -X PATCH repos/{owner}/{repo}/issues/{number} --field milestone={milestone-number}
Your task
Based on the user's request:
- View the issue to understand its scope:
gh api repos/{owner}/{repo}/issues/{number} --jq '{title, body, type: .type.name}' - Get the project item ID for the issue
- Determine appropriate Component, Priority, Size, and Type (if not set) based on the issue content
- Set all project fields using
gh project item-edit - If the issue type is not set, set it using
gh api -X PATCH - If the user specified a milestone in their request, set it using
gh api -X PATCH - Execute each step as a separate command. Do NOT chain commands with && or ;.
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.
- 2d ago First seen · 91 lines · 19 tokens per session scan A e305ff32cf7a
triage is a skill published in the GitHub repository oxidian/cc-plugins (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 600 once invoked, about $0.0001 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-30.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.