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/stevesolun/ctx/triagenpx skills add stevesolun/ctx --skill triagegit clone --depth 1 https://github.com/stevesolun/ctxWrote 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/stevesolun/ctx/triage)<a href="https://agentmods.dev/skills/stevesolun/ctx/triage"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/triage.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.00039 | $0.00523 |
| Opus 5 | $0.00019 | $0.00262 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage tracker work
Use the repository's tracker configuration and label mapping. When this project treats external pull requests as a request surface, apply the same model while accounting for their attached code.
Prefix comments created during this workflow with:
> *This was generated by AI during triage.*
Preserve the state model
Use one category role:
bugenhancement
Use one state role:
needs-triageneeds-infoready-for-agentready-for-humanwontfix
The configured tracker may map these roles to different label strings. Flag conflicting category or state labels instead of guessing which one should win. A maintainer may authorize an unusual transition.
Inspect proportionally
For queue summaries, fetch only enough context to classify and prioritize the items requested. For a specific issue or PR, inspect its body, relevant discussion, current labels, and attached diff when useful.
Check code, tests, prior decisions, and .out-of-scope/ only to the depth needed
for a trustworthy recommendation. Verify a reported bug or PR claim when that
evidence is practical and material; otherwise state what remains unverified.
Avoid re-asking questions already resolved in prior triage notes.
Recommend or act
Explain the proposed category and state with the evidence that matters. Ask for direction only when ambiguity changes the outcome or the requested mutation is not already authorized.
When applying an outcome:
needs-info: state what is known and ask specific answerable questions.ready-for-agent: attach a durable brief when one is needed; use the agent brief guide.ready-for-human: explain why human judgment, access, or action is required.wontfix: explain the reason before closing. Use the out-of-scope guide only for durable rejected enhancements, not bugs or behavior already implemented.needs-triage: preserve useful partial findings when a note would help.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 68 lines · 39 tokens per session scan A 79bd949bef91
triage is a skill published in the GitHub repository stevesolun/ctx (583 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 523 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…