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 XRenSiu/claude-code-forge --skill issuegit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/issue)<a href="https://agentmods.dev/skills/xrensiu/claude-code-forge/issue"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/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/xrensiu/claude-code-forge/issue"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/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.00283 | $0.03302 |
| Opus 5.5 | $0.00113 | $0.01321 |
| Sonnet 5.5 | $0.00057 | $0.00660 |
| Haiku 4.5 | $0.00028 | $0.00330 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue — 愿望变成能判真假的条目
产物是一条 GitHub issue，其 body 按 assets/issue_template.md 的段落序呈现（这是产物序——
第 5 格——出口可检，不是流程）。本文件写：issue 在世界里是什么、什么算写对、原语与出口、
建之前的门。怎么问、怎么组织材料是你的份额。
缺口（Judgment + Capability + Control）
deletion 测试：撤掉本 skill，引擎会把需求原文当 body 直接建 issue——"让搜索更快""把审核做对"。 这样的 issue 任何实现都能"通过"，下游 done_when 没有源头，review 判"越界"没有基准。缺的是 判据（可证伪长什么样）、原语（verify_issue.py 把判据的机械半边编译掉）、门 （建 issue 是公开动作：先给人看）。
世界（Σ）
- issue 是 TASK 的雏形，不是契约本身。 契约（done_when.yaml v2）由
/acceptance-spec或 /ai-dlc 从这里的 AC 内联生成；issue 里的 AC 已经是 v2 形状，所以两边不会漂移。 - 三种入口，同一模板：
feature（需求）、bug（复现 + 期望 + 实际，AC 就是"复现不再 发生"+ 回归守卫）、escape（合入后发现的缺陷：多一段"归因层 / 为什么该层的门没拦住"， 建完 issue 后必须登记：aidlc_state.py escape --slug <feature> --layer <归因层> --why "<为什么没拦住>" --issue <N> --by <人>——它计到归因层、追加escape-defects.md、镜像进specs/<slug>/；运行时目录已清时加--root specs。 只写 issue 不登记，/retro的逃逸率永远是 0——它是世界层唯一的外部校准源，断在这里等于没有校准）。 - 两条轨道。 语义份额 × 变化率高、实现原语难度低 → PSL 轨（先
/psl建世界 → G1 人签， 再回来建 issue）；确定性主导 → TASK 轨直接建。混合需求只对体验性内核走 PSL。速判：把需求 交给不了解产品的工程师照字面做，会不会做出"技术正确、产品错误"的东西？会 → PSL。 客观触发有两条，都不靠自评（Ambig-SWE：模型分不清任务写没写清楚）： ①--dos dos.yaml时依赖 DOS:出现 dos.yaml 解析不了的概念 → 强制 PSL 轨。 前提是闭包真的被算过：没有dos.yaml时这条判据不是失败也不是通过，是没算， 而没算过的判据挡不住"自信而错的人绕开 G1"。所以 M / L 档带--require-dos—— 它先在项目目录里自动发现dos.yaml（../ai-dlc/scripts/repo_assets.py：仓库根 /docs//ontology/），找不到才拒，并告诉你去跑/dos-extract并把它提交进 git （全组共用一份，不放.aidlc/）。落地状态看aidlc_state.py repo； ② TASK 轨在 issue 之后、G2 之前，对同一个 issue 隔离起草 2–3 份 done_when，跑../donewhen-extract/scripts/divergence.py：分歧率超阈值 → 那些分歧就是必须澄清的槽 （每条自带要问用户的话）。详见references/dual-track.md。 - 范围段四项（做 / 不做 / 硬约束 / 成功度量）是人写的："做到哪儿为止"agent 推不出来。 你可以起草，但每项都要让用户确认或改。
- 假设台账：澄清最多 3 轮；答不上来的承重槽不默认填，写进台账：假设 · 绑定的 REQ/AC · 风险 · 到期验证点（哪个 AC 或哪道门验证它）。超时不是失败，是带风险签字继续。
- 关于用户的 Σ："快一点""稳定""大部分"是日常语言，不是判据——把它翻译成数字时，数字
的来源要么是用户给的、要么是 SLO/KPI、要么是一次真实失败；没有来源就
needs_threshold_source标出来问，不编。
判据（φ）：什么算写对了
What ships with it
20 files 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.
- assets/bug_extra.md 399 B
- assets/escape_extra.md 442 B
- assets/issue_template.md 2.7 KB
- eval/fixtures/bad_filepath_observe.md 1.7 KB
- eval/fixtures/bad_no_twin.md 1.4 KB
- eval/fixtures/bad_vague.md 1.6 KB
- eval/fixtures/card-root/invariants/fixture.card.yaml 375 B
- eval/fixtures/closure_fail.md 1.7 KB
- eval/fixtures/dos.yaml 163 B
- eval/fixtures/good_bug.md 1.8 KB
- eval/fixtures/good_issue.md 1.7 KB
- eval/fixtures/territory_invariant_known.md 1.7 KB
- eval/fixtures/territory_invariant_unknown.md 1.7 KB
- eval/fixtures/twin_points_at_happy.md 1.7 KB
- eval/fixtures/twin_reverse_paired.md 1.7 KB
- eval/gate.json 1.9 KB
- eval/report.md 1.7 KB
- references/acceptance-shape.md 2.2 KB
- references/dual-track.md 1.4 KB
- scripts/verify_issue.py 27 KB runs code
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 · +9 lines dd1358f2525d
- 1mo ago Changed 3698e16a4585
- 1mo ago Changed · +2 lines 6415d7dd2e37
- 1mo ago Changed 60b820a2590a
- 1mo ago Changed · +7 lines 79c259e9b6c4
- 1mo ago Changed b130b59d1b5c
- 1mo ago Changed · +3 lines e0d5b1ccfd36
- 1mo ago First seen · 115 lines · 283 tokens per session scan A 0053db4d6b30
issue is a skill published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 283 tokens to every session and 3,302 once invoked, about $0.0011 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-09-05.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…