agentmods.dev

daily-bugfix-check

daily-bugfix-check is a skill for Claude Code, Codex from Kevin-Liu-01/Agent-Machines. It costs 71 tokens per session (475 once invoked), scanned A, original, MIT.

A daily review that examines the current author's commits from the previous 24 hours and looks for bugs they introduced.

In plain words
What is it for?
Use it to inspect recent changes, check for defects such as missing imports or logic errors, and fix confirmed bugs.
Why use it?
It helps catch regressions soon after code is written, before they spread into later work or production.

Skill for Claude CodeCodex

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

not rated 29repo +1 15d ago A scan SkillSpector: pass 71 tokens original MIT

Good fit Use it to inspect recent changes, check for defects such as missing imports or logic errors, and fix confirmed bugs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kevin-liu-01/agent-machines/daily-bugfix-check
View source ↗ Kevin-Liu-01/Agent-Machines agent-machines.dev
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 Kevin-Liu-01/Agent-Machines --skill daily-bugfix-check
Clone the repo
git clone --depth 1 https://github.com/Kevin-Liu-01/Agent-Machines

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 daily-bugfix-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/daily-bugfix-check/github.svg)](https://agentmods.dev/skills/kevin-liu-01/agent-machines/daily-bugfix-check)
Your own site
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/daily-bugfix-check"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/daily-bugfix-check/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.

agentmods 80×15 button for daily-bugfix-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/daily-bugfix-check"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/daily-bugfix-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 475 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.00475
Opus 5.5 $0.00028 $0.00190
Sonnet 5.5 $0.00014 $0.00095
Haiku 4.5 $0.00007 $0.00047

Measured 2mo ago against content hash aa324b95da1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

daily-bugfix-check 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 2mo 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.

knowledge/skills/daily-bugfix-check/SKILL.md · 63 lines

What it actually says

Daily Bugfix Check

Overview

Proactively review the current author's commits from the last 24 hours, identify any bugs or issues introduced, and fix them. This is a combined workflow that scopes to the last day and applies the recent-code-bugfix pattern.

Workflow

1) Identify recent commits

git config user.name
git log --since="24 hours ago" --author="<author>" --stat --format='%H %s'

Collect the list of files touched in the last 24 hours by the current author.

2) Analyze changes for potential issues

For each changed file:

  • Run ReadLints to check for linter errors
  • Read the recent diffs to look for:
    • Undefined variable or function references
    • Missing imports after refactoring
    • Type mismatches or broken interfaces
    • Functions called with wrong argument counts
    • Stale references to moved/renamed code
    • Copy-paste errors
    • Logic errors (wrong conditions, off-by-one, missing null checks where critical)

3) Triage findings

Categorize found issues:

  • Bugs: Definite defects that will cause runtime errors or incorrect behavior
  • Warnings: Potential issues that may cause problems in edge cases
  • Style: Non-functional issues (skip these, not in scope)

Only proceed to fix Bugs. Report Warnings for the user's awareness.

4) Fix bugs

For each confirmed bug, apply the recent-code-bugfix workflow:

  • Make minimal, targeted fixes
  • Follow project conventions
  • Verify with linter after each fix

5) Report

Summarize findings:

  • Total commits reviewed and files analyzed
  • Bugs found and fixed (with root cause tied to specific commits)
  • Warnings identified (for user awareness)
  • If no bugs found, say so clearly
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. 2mo ago First seen · 63 lines · 71 tokens per session scan A aa324b95da1e

Subscribe to this mod's changes

daily-bugfix-check is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed 15d ago), licensed MIT. It adds 71 tokens to every session and 475 once invoked, about $0.0003 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-08-30.

Claude CodeCode reviewDebuggingai-agentcronhermes-agentmcpmicrovmmodel-context-protocol
Related

daily-bugfix-check compared with skills from other repositories

daily-bugfix-check next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
daily-bugfix-checkKevin-Liu-01/Agent-MachinesSkill2915d agoMITA71Claude Code, Codex
patch-editnexu-io/open-designSkill106kyesterdayApache-2.0A30Claude Code, Codex
second-opinionSinanTufekci/agent-internSkill30yesterdayMITA86Claude Code
self-improving-skills-reviewUniM0cha/self-improving-skillsSkill511mo agoMITA68Codex
app-debug-workflowMilkyWay008/Hermes-OTGSkill222mo agoMITA64Claude Code, Codex
code-simplifiercyanheads/mcp-reporterSkill131mo agoApache-2.0A23Claude Code, Codex
grill-with-docspedroiff0/awesome-skillsSkill115d agoMITA36Claude Code, Codex