fix-verification-plan

fix-verification-plan is a skill for Claude Code, Codex from BingHanOfUESTC/open_agent_team. It costs 0 tokens per session (36 once invoked), scanned A, original, MIT.

A checklist for verifying each software fix with unit tests, integration tests, manual reproduction, regression checks, monitoring or log checks, and rollback signals.

In plain words
What is it for?
Planning how to test a bug fix, confirm its effects in production signals, and decide when to undo it.
Why use it?
It reduces the chance that a fix only appears to work or causes a new problem.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Planning how to test a bug fix, confirm its effects in production signals, and decide when to undo it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/binghanofuestc/open_agent_team/fix-verification-plan
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.

Any agent
npx skills add BingHanOfUESTC/open_agent_team --skill fix-verification-plan
Clone the repo
git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team

Made for: Claude Code, Codex.

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 fix-verification-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/fix-verification-plan.svg)](https://agentmods.dev/skills/binghanofuestc/open_agent_team/fix-verification-plan)
Your own site
<a href="https://agentmods.dev/skills/binghanofuestc/open_agent_team/fix-verification-plan"><img src="https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/fix-verification-plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 36 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.00000 $0.00036
Opus 5 $0.00000 $0.00018
Sonnet 5 $0.00000 $0.00007
Haiku 4.5 $0.00000 $0.00004

Measured 8d ago against content hash 70aca2b7acb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

fix-verification-plan 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 8d 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.

teams/bug_triage_team/skills/fix-verification-plan/SKILL.md · 13 lines

What it actually says

Fix Verification Plan

For each fix:

unit test
integration test
manual reproduction check
regression check
monitoring/log check
rollback signal
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. 8d ago First seen · 13 lines · 0 tokens per session scan A 70aca2b7acb4

Subscribe to this mod's changes

fix-verification-plan is a skill published in the GitHub repository BingHanOfUESTC/open_agent_team (109 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 36 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-30.

Related

Other skills, from other repositories

cdt

Multi-agent development workflow using Agent Teams. Supports five modes: plan (architect teammate + PM teammate debate → plan.md), dev (developer teammate + code-tester teammate + qa-tester teammate + reviewer teammate iterate → code), full (plan → approval gate → dev), auto (plan → dev, no gate), and bugfix (tester +…

rube-de/cc-skills · 96 tokens

stellar-forge

Eval-driven coding harness for building production Stellar dApps. Routes tasks to 6 specialist agents, verifies output with structured evals, steers on failure, e2e-tests with Stellar Agentic Kit hooks, and knowledge-graphs every project. Use when building any Stellar app — tokens, DeFi, NFTs, payment APIs, or full…

rylsherdamz-rgb/stellar-forge · 82 tokens

dlc

Dev Life Cycle quality gates: run security scans, code quality checks, performance analysis, test coverage, and PR review compliance. Routes to domain-specific sub-skills or runs all checks in sequence.

rube-de/cc-skills · 42 tokens

fix-failing-tests

Iteratively fix all failing tests until the test suite is green.

KnoxOps/agent-runbook · 17 tokens

textual-ui-developer

Develop and debug the MassGen Textual TUI with deterministic replay, snapshot regression tests, and targeted runtime checks.

massgen/MassGen · 29 tokens

verify

Verify recent code changes work end-to-end by building, running tests, and exercising affected features. Use when the user asks to verify changes, requests "/verify", or wants confirmation a feature actually works.

qinghaoliqaq/AutoCoder · 42 tokens