A bug-fixing workflow that researches an issue, checks the relevant code and documentation, proposes a solution, implements it, verifies it locally, and prepares a pull or merge request.

Use it with an issue-tracker ticket to gather context, plan the fix, apply the change, run local checks, and deliver review-ready work.

It gives bug work a defined path from root-cause analysis through approval and verification instead of jumping straight into edits.

dev-fix — Skill for Codex by HoangNguyen0403/agent-skills-standard

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 HoangNguyen0403/agent-skills-standard --skill dev-fix

Clone the repo

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/dev-fix/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/dev-fix)

Your own site

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/dev-fix"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/dev-fix/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/dev-fix"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/dev-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,776 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.01776
Opus 5.5	$0.00017	$0.00710
Sonnet 5.5	$0.00009	$0.00355
Haiku 4.5	$0.00004	$0.00178

Measured 27d ago against content hash 22f215d9516c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dev-fix 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 27d 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.

.codex/skills/dev-fix/SKILL.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev Fix Skill

[!IMPORTANT] Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.

Instructions

When the user asks to perform this workflow, execute the following steps:

Dev-Fix — Bug Remediation

Goal: Take a bug ticket from root-cause analysis through a locally-verified PR/MR, enforcing a strict Propose -> Approve -> Verify cycle.

Input

/dev-fix <issue-url-or-key>

Workflow

Step 0: Environment Prep (Turbo)

// turbo

Sync Registry: git pull origin main in the standard repo.

Step 1: Research & Discovery (Implementation Plan Phase)

[!TIP] Sub-Agent Delegation: If your platform supports sub-agents, delegate ticket extraction to specialist-jira-analyst and context lookup to specialist-codebase-scout. If sub-agents are NOT supported, execute these steps yourself.

Analyze Ticket: Use installed Jira/GitHub/GitLab/ADO MCP first; otherwise use exported ticket text. Extract Reproduce steps, Expected Result, and Actual Result.
Cross-Check Context: Use knowledge-base MCP when configured; otherwise use local code search. Locate relevant code.
Create Implementation Plan:
- Use the Implementation Plan Template below.
- Initialize project-local docs/prd/prd-plan-[slug].md.
- Goal: Clear description of the root cause.
- Proposed Changes: Exact files and logic to be modified.
- Verification Plan: Detail which QE skill will be used to verify the fix locally before PR.
- Do not propose code changes until repro steps, expected result, and root cause hypothesis are explicit.
- SNC: score per common-task-complexity-routing; record snc_tier/model_tier in the plan.
HARD STOP: Request user approval for the implementation plan. Mandatory at snc_tier=high; medium requires self-review first; low may skip approval in autonomous mode only.
Readiness Gate: Run implementation-readiness; code only after READY or approved PARTIAL.

Read the full file on GitHub · 181 lines

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.

27d ago Changed · +1 lines 22f215d9516c
1mo ago Changed · -2 lines dd679cb74e6d
1mo ago Changed 2a1486e5149f
1mo ago Changed · +2 lines 07ac53818341
1mo ago First seen · 180 lines · 43 tokens per session scan A 497177eb182f

Subscribe to this mod's changes

dev-fix is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,776 once invoked, about $0.0002 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-03.

Debugging Git and workflow React best-practices coding-standards flutter nestjs nextjs

inspector-workbench

Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…

CopilotKit/CopilotKit · 112 tokens

perf-optimization

Profile-driven performance optimization protocol. Use when profiling data (CPU, heap, trace) is available or when the user requests performance analysis. Covers methodology (Profile → Analyze → Opportunity Scan → Prioritize → Optimize → Benchmark), optimization pattern catalog, safety invariants, and when-to-stop…

irahardianto/awesome-agv · 72 tokens

dev-fix