BUG逐条修复

A bug-fixing command that assigns separate bugs to separate sub-agents while one coordinator directs the work.

In plain words
What is it for?
Use it when fixing multiple bugs in parallel, with each fix investigated and carried out independently.
Why use it?
It separates fixes so each sub-agent handles only one bug and requires research before changes are made.

Command

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 commands/nongjun/awesome-harness-engineering/bug
Clone the repo
git clone --depth 1 https://github.com/nongjun/awesome-harness-engineering
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 43 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00043
Opus 5 $0.00000 $0.00022
Sonnet 5 $0.00000 $0.00009
Haiku 4.5 $0.00000 $0.00004

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

Security

Grade A, and why

BUG逐条修复 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.

commands/BUG逐条修复.md · 2 lines

What it actually says

请修复,分配多个子 agent 去执行,你只做指挥,但是每一个子 agent 只能去修复一条,并且修复前要做好充分的研究不能盲目!

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. 2d ago First seen · 2 lines · 0 tokens per session scan A 86601af80fbc

Subscribe to this mod's changes

BUG逐条修复 is a command published in the GitHub repository nongjun/awesome-harness-engineering (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 43 tokens. 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.