bug

A command that records a reported software bug as a recoverable local Workflow draft. It records the issue only and does not start fixing it or turn it into a development task.

In plain words
What is it for?
Use it to save a bug description locally as a Workflow bundle for later handling through the Workflow upload command.
Why use it?
It preserves the original bug report while checking for duplicates and dependencies, so the issue can be reviewed or uploaded later without beginning implementation.

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/go1c/workflow-plugin/bug
Clone the repo
git clone --depth 1 https://github.com/Go1c/workflow-plugin
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 122 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.00020 $0.00122
Opus 5 $0.00010 $0.00061
Sonnet 5 $0.00004 $0.00024
Haiku 4.5 $0.00002 $0.00012

Measured yesterday against content hash e60df057db4f, 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 yesterday.

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 · 10 lines

What it actually says

调起 workflow-ops 技能的记 bug 流程处理下面这条 bug。预设边界:只记录,不启动修复,不扩写成开发任务。先按技能要求全局查重和分析依赖,再生成本地 bundle;线上写入统一交给 /workflow:upload,按当前权限模式执行并读回。

用户描述原文(即 bug 现象):

$ARGUMENTS

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. yesterday First seen · 10 lines · 20 tokens per session scan A e60df057db4f

Subscribe to this mod's changes

bug is a command published in the GitHub repository Go1c/workflow-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 122 once invoked, about $0.0001 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.