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 skills add asherzj/ashers-agent-skills --skill flow-incoming-issuegit clone --depth 1 https://github.com/asherzj/ashers-agent-skillsWrote 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/asherzj/ashers-agent-skills/flow-incoming-issue)<a href="https://agentmods.dev/skills/asherzj/ashers-agent-skills/flow-incoming-issue"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/flow-incoming-issue/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/asherzj/ashers-agent-skills/flow-incoming-issue"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/flow-incoming-issue.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.00461 |
| Opus 5 | $0.00029 | $0.00230 |
| Sonnet 5 | $0.00012 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
flow-incoming-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 10d 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
外部 Issue 处理流程
用明确的状态门禁组合 triage 和 implement。开始前读取仓库配置、工单系统说明、分诊标签映射、相关领域术语和 ADR。
边界
本流程只处理团队没有通过 to-tickets 创建的外部工作。拆票生成的工单天然可由代理执行，应直接进入 implement。
流程
- 对指定 Issue 或外部 PR 调用
triage。由它负责收集上下文、验证事实、维护者检查点、AI 声明、代理简报、标签和拒绝事项的关闭动作。 - 检查产生的规范状态：
needs-triage或needs-info：停止实现，说明还需要什么信息或维护者决策。ready-for-human：停止，并把简报留给人类。wontfix：停止；事项已经终结。ready-for-agent：状态允许代理实现，但仍要服从用户本次请求的范围。
- 只有事项为
ready-for-agent，且用户要求本流程继续完成交付时，才调用implement。如果用户只要求分诊，即使事项已就绪也应停在分诊结果。
如果事项一开始就是 ready-for-agent，先确认它只有一个状态标签并包含耐久的代理简报，然后跳过重复分诊，直接进入实现。一张 Issue 始终是一份实现单元。
完成条件
分别汇报分诊结果和实现结果。只有实际完成验证、评审、提交、推送和工单收尾后，才能称为已交付；仅完成分诊不能称为交付。
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.
- 10d ago First seen · 30 lines · 58 tokens per session scan A 41cf73830ad1
flow-incoming-issue is a skill published in the GitHub repository asherzj/ashers-agent-skills (2 stars, last pushed 13d ago), licensed MIT. It adds 58 tokens to every session and 461 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.