Borrowing it
Nothing to install: this file belongs to roryeckel/wyoming_openai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/roryeckel/wyoming_openai/main/.agents/skills/community-triage/SKILL.mdgit clone --depth 1 https://github.com/roryeckel/wyoming_openaiWrote 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/roryeckel/wyoming_openai/community-triage)<a href="https://agentmods.dev/skills/roryeckel/wyoming_openai/community-triage"><img src="https://agentmods.dev/badge/skills/roryeckel/wyoming_openai/community-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/roryeckel/wyoming_openai/community-triage"><img src="https://agentmods.dev/badge/skills/roryeckel/wyoming_openai/community-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 2 findings, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 17 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
- low Excessive Agency · line 192 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00059 | $0.02276 |
| Opus 5 | $0.00030 | $0.01138 |
| Sonnet 5 | $0.00012 | $0.00455 |
| Haiku 4.5 | $0.00006 | $0.00228 |
Grade A, and why
community-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 12d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Triage
Handle community issues and PRs with respect, evidence, and firm scope discipline.
This skill exists to protect maintainer time, avoid speculative changes, and preserve the project's intended boundary.
Project Boundary
- Wyoming OpenAI is an OpenAI-compatible proxy/middleware.
- Treat OpenAI-compatible request/response behavior as the primary contract.
- Existing backend enum/autodetection exceptions are compatibility shims, not a license to support arbitrary provider-specific transports, routes, or schemas.
- Do not expand scope to custom endpoints such as
/tts, provider-specificstream=truesemantics, or bespoke response formats unless the maintainer explicitly chooses to widen scope.
Goals
- Be helpful without overcommitting.
- Separate local defects from upstream limitations and unsupported integrations.
- Prefer minimal actionable next steps: fix locally, request reproduction details, route upstream, or close with clear reasoning.
- Maintain a respectful tone even when issue quality is low.
Default Posture
- Assume good faith.
- Do not mirror vague or incorrect technical framing.
- Translate the report into the actual technical question the project can answer.
- Use evidence from code, tests, docs, and upstream behavior before concluding.
- Do not let conversation momentum expand the project's scope by accident.
Triage Workflow
- Classify the thread.
- Identify the supported surface.
- Gather evidence.
- Decide ownership.
- Respond with a clear outcome.
1. Classify the thread
Choose the closest category:
- bug/regression on a supported surface
- feature request inside scope
- feature request outside scope
- support question or configuration issue
- upstream compatibility issue
- low-fidelity report with insufficient reproduction
- community PR
2. Identify the supported surface
Pin down the exact surface before deciding anything:
- endpoint path
- Wyoming event flow
- CLI/config flag
- backend compatibility path
- testable request/response behavior
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.
- 12d ago First seen · 295 lines · 59 tokens per session scan A 365ec787180c
community-triage is a skill published in the GitHub repository roryeckel/wyoming_openai (210 stars, last pushed 3d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,276 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-30.
Other skills, from other repositories
development-estimation
Use when estimating time, effort, cost, or complexity for features, projects, refactors, and bug backlogs. Produces defensible estimates via triage, decomposition, risk handling, and confidence intervals, with clear assumptions and validation steps.
home-assistant-hermes-voice-pipeline
Use when debugging the Hermes + Harper HA voice pipeline.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.