What is analyze-issue?

A workflow for examining a GitHub Issue, the discussion record used to describe a bug or task, and documenting what needs to be done. It creates a task file and a requirements analysis without changing product code.

Use it to inspect an issue, search the related code, create task-tracking files, and record the analysis in `analysis.md`.

It gives developers a written understanding of the issue, affected code, risks, and dependencies before implementation begins.

analyze-issue — Skill by ModelEngine-Group

Install

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.

agentmods

npx agentmods add skills/modelengine-group/fit-framework/analyze-issue

Any agent

npx skills add ModelEngine-Group/fit-framework --skill analyze-issue

Clone the repo

git clone --depth 1 https://github.com/ModelEngine-Group/fit-framework

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 288 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00042	$0.00288
Opus 5	$0.00021	$0.00144
Sonnet 5	$0.00008	$0.00058
Haiku 4.5	$0.00004	$0.00029

Measured 2d ago against content hash 0bcff9fda556, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analyze-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 2d 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.

.agents/skills/analyze-issue/SKILL.md · 41 lines

What it actually says

分析 Issue

分析指定的 GitHub Issue 并创建任务文件。

执行步骤

获取 Issue 信息:

gh issue view <issue-number> --json number,title,body,labels

生成任务ID:
```
date +%Y%m%d-%H%M%S
```
创建任务目录:
```
mkdir -p .ai-workspace/active/TASK-<timestamp>/
```
基于 .agents/templates/task.md 模板创建 task.md，填写任务元数据。
执行需求分析（仅分析，不编写业务代码）:
- 阅读并理解 Issue 描述
- 搜索相关代码文件（只读不改）
- 分析代码结构和影响范围
- 识别技术风险和依赖
输出分析文档到 analysis.md。
更新任务状态，标记 requirement-analysis 为完成。
提示下一步使用 plan-task skill。

注意: 禁止编写或修改任何业务代码，只做分析。

Changes

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.

2d ago First seen · 41 lines · 42 tokens per session scan A 0bcff9fda556

Subscribe to this mod's changes

analyze-issue is a skill published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 288 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.

Planning Project management agentic-ai ai plugin plugin-system

backlog-tpm

Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…

timgranlundmarsden/claude-agent-flow · 88 tokens

backlog-md

Task and document management with Backlog.md. Use this skill whenever working with tasks, tracking work, creating subtasks, searching or viewing existing tasks, or any time work should be preserved across sessions or handed off. Triggers include: "create a task", "track this", "add to backlog", "what tasks do I have"…

timgranlundmarsden/claude-agent-flow · 136 tokens

parallel-feature-development

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…

wshobson/agents · 105 tokens

analyze-issue