Borrowing it
Nothing to install: this file belongs to xrf9268-hue/aiops-platform. 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/xrf9268-hue/aiops-platform/main/.claude/skills/handle-issue/SKILL.mdgit clone --depth 1 https://github.com/xrf9268-hue/aiops-platformWrote 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/xrf9268-hue/aiops-platform/handle-issue)<a href="https://agentmods.dev/skills/xrf9268-hue/aiops-platform/handle-issue"><img src="https://agentmods.dev/badge/skills/xrf9268-hue/aiops-platform/handle-issue.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.1 | $0.00060 | $0.04041 |
| Opus 5 | $0.00030 | $0.02021 |
| Sonnet 5 | $0.00012 | $0.00808 |
| Haiku 4.5 | $0.00006 | $0.00404 |
Grade A, and why
handle-issue 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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handle Issue #$ARGUMENTS
本仓库是 OpenAI Symphony SPEC 的 Go 端口，SPEC 对齐是硬要求。本 skill 覆盖 issue → 开 PR 阶段；PR 之后交给 handle-pr（SPEC 对齐审查轮）+ gh-pr-follow-through（盯到 merge-ready）。
审查 / 合并协议是共享的。 pre-push 双 reviewer、
@codex review收敛、GraphQL review threads、PR-body 活账本、合并门槛、回归+变异测试纪律统一在docs/runbooks/pr-review-merge-protocol.md。本 skill 只写 issue→PR 阶段差异，到 push/审查/合并步骤直接照那份协议执行，不在此复述。
何时用 / 不该用
- 用：要开始处理本仓库一个已建的 GitHub issue（"处理下一个 issue"、"修 #N"、"实现这个 issue"）。
- 不该用：PR 已存在 → 用
handle-pr+gh-pr-follow-through；无需 SPEC/upstream 调研的琐碎改动；非 GitHub 的 tracker。
上下文就位（issue 全文 + upstream 镜像 + main HEAD）
!bash .claude/skills/handle-issue/scripts/bootstrap.sh "$ARGUMENTS" 2>&1
scripts/bootstrap.sh（set -euo pipefail，fail-fast）依次做：校验参数为数字 issue 号（坏参数 exit 2，与后续 fetch 失败区分）→ 校验/刷新 SPEC 上游镜像 /tmp/symphony-upstream（origin 不是 symphony 就重新 clone；pull --ff-only/clone 失败即中止，不留陈旧镜像）→ 打印 issue 全文（pin --repo，不截断）→ git fetch origin main 后打印 main HEAD（fetch 失败即中止，无管道掩盖状态）。
开工前完整读 issue 正文，尤其逐条 Acceptance criteria。SPEC 文本歧义时直接 grep /tmp/symphony-upstream/elixir/lib/symphony_elixir/*.ex 找原算法/分支，不要用 WebFetch 总结。
流程（按序）
1. 读 issue + 并行 owner 探测（协议 §8 issue-phase 推论）
读 labels（area:spec-alignment / priority:pN / type:*）与正文。把正文的 Acceptance criteria 复选框当作 definition-of-done——每条都要满足或显式说明为何不在范围内。
动手前先执行协议 §8 的 issue-phase 探测，判定命令与处置路由全部以 docs/runbooks/pr-review-merge-protocol.md §8 为唯一来源，照其结果执行。模式自主选定并通报，不询问。
1.5 负面约束 preflight（设计 / 边界类 issue 必须）
如果 issue 引用了 design doc、runbook、SPEC boundary、redaction/retention rule、non-goal list，或正文里出现 "do not store / parse / mutate / persist / automate / gate" 这类负面约束，写代码前先写短 guardrail。至少列出：
- Required behavior：必须生成 / 修改 / 证明什么。
- Negative constraints：不得存储、解析、变更、持久化、自动化、当成 gate 的东西。
- Opaque boundaries：哪些输入是任意 human / agent / protocol text，除非 issue 明确要求 parser，否则不得解析。
- Design challenge：如果 redaction / retention 需求看起来必须靠 grammar / parser / heuristic 理解自由文本才能满足，先停下，说明为什么 opaque omission 不够。
What ships with it
1 file 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.
- 7d ago First seen · 111 lines · 60 tokens per session scan A 8cb44cbc65d4
handle-issue is a skill published in the GitHub repository xrf9268-hue/aiops-platform (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 60 tokens to every session and 4,041 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-31.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
cmux-testing
A regression test for a bug fix ships as two commits so CI proves the test catches the bug.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
quick
/quick — Lightweight Feature Workflow.