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 ChianW/C31 --skill c31-workflow-bug-reproductiongit clone --depth 1 https://github.com/ChianW/C31Wrote 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/chianw/c31/c31-workflow-bug-reproduction)<a href="https://agentmods.dev/skills/chianw/c31/c31-workflow-bug-reproduction"><img src="https://agentmods.dev/badge/skills/chianw/c31/c31-workflow-bug-reproduction/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/chianw/c31/c31-workflow-bug-reproduction"><img src="https://agentmods.dev/badge/skills/chianw/c31/c31-workflow-bug-reproduction.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.00053 | $0.00607 |
| Opus 5 | $0.00026 | $0.00303 |
| Sonnet 5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
C31-workflow-bug-reproduction 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 9d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multilingual Triggers
| Language | Trigger phrases |
|---|---|
| EN | C31-workflow-bug-reproduction |
| ZH | 复现bug, bug复现 |
| JA | バグ再現, 再現手順 |
Output language: Respond automatically in the user's conversation language.
C31-workflow-bug-reproduction
Systematic bug reproduction and isolation. Read-only — never writes code.
When to Use
- Bug report lacks clear reproduction steps
- Need to determine if bug is environmental or code-level
- Creating a regression test for a reported issue
- Bug only appears in CI/production but not locally
- User says "it doesn't work" without specifics
Input
User provides:
- Bug symptom (what's wrong)
- Environment where it occurs (OS, versions, config)
- Any existing reproduction steps (even partial)
- Whether it reproduces consistently or intermittently
Reproduction Flow
-
Form hypotheses — List 3 likely causes ranked by probability:
- Code bug (logic error, race condition)
- Environment issue (wrong version, missing dependency, stale state)
- Config issue (wrong flag, missing env var)
-
Minimize surface area:
- Strip unrelated code/config
- Use minimal dataset
- Disable caching, async, or concurrency if possible
- Test with defaults before custom config
-
Controlled experiments:
- Change one variable at a time
- Document each result
- If intermittent, run N times and log frequency
-
Verify reproduction:
- Reproduces on clean environment? → code bug
- Only reproduces on specific env? → environment/config bug
- Doesn't reproduce at all? → missing condition or fixed already
Output Format
## Bug Reproduction: [brief description]
**Hypotheses tested**:
| # | Hypothesis | Result | Evidence |
**Minimal reproduction**:
[steps or code that reliably triggers the bug]
**Root cause category**: [code / environment / config / cannot reproduce]
**Additional conditions required**: [if any]
**Recommended next step**: [fix / deeper investigation / environment change]
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.
- 9d ago First seen · 82 lines · 53 tokens per session scan A 9abacde2a0da
C31-workflow-bug-reproduction is a skill published in the GitHub repository ChianW/C31 (1 stars, last pushed 14d ago), licensed MIT. It adds 53 tokens to every session and 607 once invoked, about $0.0003 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.
Other skills, from other repositories
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
oia-manifest
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
create-harness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…
example-harness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.