CataForge: Command for Claude Code

.claude/commands/framework-issue-resolve.md

framework-issue-resolve is a command for Claude Code from lync-cyber/CataForge. It costs 27 tokens per session (285 once invoked), scanned A, original, MIT.

A command workflow for reviewing and resolving upstream GitHub issues, which are reports or requests tracked in a project's online code repository.

In plain words
What is it for?
Use it to triage CataForge issues, write improvement reviews, propose a fix, implement approved changes, open a pull request, and close the issue after merging.
Why use it?
It separates issue analysis, maintainer approval, code changes, pull-request merging, and closure so issues are not changed or closed prematurely.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is lync-cyber/CataForge's own configuration. It tells Claude Code how to work on CataForge itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything CataForge configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lync-cyber/CataForge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/lync-cyber/CataForge/main/.claude/commands/framework-issue-resolve.md
Clone the repo
git clone --depth 1 https://github.com/lync-cyber/CataForge

Made for: Claude Code.

Wrote 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.

agentmods badge for framework-issue-resolve

README.md
[![agentmods](https://agentmods.dev/badge/commands/lync-cyber/cataforge/framework-issue-resolve/github.svg)](https://agentmods.dev/commands/lync-cyber/cataforge/framework-issue-resolve)
Your own site
<a href="https://agentmods.dev/commands/lync-cyber/cataforge/framework-issue-resolve"><img src="https://agentmods.dev/badge/commands/lync-cyber/cataforge/framework-issue-resolve/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.

agentmods 80×15 button for framework-issue-resolve

Your own site · 80×15
<a href="https://agentmods.dev/commands/lync-cyber/cataforge/framework-issue-resolve"><img src="https://agentmods.dev/badge/commands/lync-cyber/cataforge/framework-issue-resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 285 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00285
Opus 5.5 $0.00011 $0.00114
Sonnet 5.5 $0.00005 $0.00057
Haiku 4.5 $0.00003 $0.00028

Measured 2mo ago against content hash 4d091ee86455, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

framework-issue-resolve 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 2mo 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.

.claude/commands/framework-issue-resolve.md · 16 lines

What it actually says

按 .cataforge/skills/framework-issue-resolve/SKILL.md 的五步闭环处理上游 GitHub issue:

  1. 拉取:cataforge issue triage --dry-run 看 verdict 表
  2. 分析:写 SKILL-IMPROVE 草稿到 docs/reviews/triage/SKILL-IMPROVE-<id>-issue-<N>.md
  3. 判定:给 verdict + rationale + 修复路径(maintainer go/no-go)
  4. 实施:feature 分支 + Edit + commit + PR(标准 dev 流程,见 CLAUDE.md §Git 工作流)
  5. 关闭:PR merge 后 cataforge issue close <N> --verdict fixed --pr <P>

调度时先 Read 上述 SKILL.md 拿完整协议(含 verdict 五态、close comment 模板、Anti-Patterns)。

硬约束:步骤 3↔4 是 maintainer 强制 checkpoint。未拿到明确 go-ahead 前不写代码改动;PR 未 merge 前不 close issue。

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.

  1. 2mo ago First seen · 16 lines · 27 tokens per session scan A 4d091ee86455

Subscribe to this mod's changes

framework-issue-resolve is a command published in the GitHub repository lync-cyber/CataForge (128 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 285 once invoked, about $0.0001 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.