Borrowing it
Nothing to install: this file belongs to ivanarama/onebase. 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/ivanarama/onebase/main/.agents/skills/triage-issues/SKILL.mdgit clone --depth 1 https://github.com/ivanarama/onebaseWrote 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/ivanarama/onebase/triage-issues)<a href="https://agentmods.dev/skills/ivanarama/onebase/triage-issues"><img src="https://agentmods.dev/badge/skills/ivanarama/onebase/triage-issues/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/ivanarama/onebase/triage-issues"><img src="https://agentmods.dev/badge/skills/ivanarama/onebase/triage-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- medium Agent Snooping · line 8 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00073 | $0.00491 |
| Opus 5.5 | $0.00029 | $0.00196 |
| Sonnet 5.5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
triage-issues 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.
What it actually says
Codex-адаптер триажа
- До любых действий с репозиторием или GitHub полностью прочитать каноническую процедуру
.claude/skills/triage-issues/SKILL.md. - Следовать ей с обычным приоритетом инструкций Codex: слово
headlessне отменяет системные ограничения, безопасность или необходимость сообщить настоящий блокер. - До записи в GitHub проверить доступность
gh, действующую аутентификацию иgh api user --jq .login. Писать разрешено только отivanarama; иначе остановиться без изменений. Непосредственно перед первой записью перечитать метки и маркеры кандидата, чтобы не пересечься с параллельным прогоном. - Считать
$triage-issuesCodex-эквивалентом/triage-issues. Упоминания следующих этапов — только описание маршрута, не разрешение запускать их автоматически. - Разрешать пути от корня, найденного через
git rev-parse --show-toplevel. Не обновлять грязный или общийmainповерх пользовательских изменений; послеgit fetchиспользовать уже синхронный checkout либо изолированный worktree отorigin/main. - На Windows использовать PowerShell-эквиваленты команд, сохраняя семантику и проверку кодов возврата. До сборки или тестов проверить доступность
go; отсутствие обязательного инструмента не маскировать успешным результатом. - Сохранять полномочия, критерии, лимиты, маркеры
pp:*, GitHub-метки и точный форматИТОГ:из канонической процедуры.
Логика конвейера живёт только в канонической процедуре. Этот файл содержит лишь слой совместимости Codex.
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 Changed · -255 lines · -12 tokens per session 3ff6c8d733a2
- 2mo ago First seen · 272 lines · 85 tokens per session scan A 3f92ebc441aa
triage-issues is a skill published in the GitHub repository ivanarama/onebase (135 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 491 once invoked, about $0.0003 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-30.
Other skills, from other repositories
sap-session
A guided evidence-review process for diagnosing SAP operations without direct access to the live system, with a person collecting evidence and the agent reviewing it.
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.