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 Kevin-Liu-01/Agent-Machines --skill daily-bugfix-checkgit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/daily-bugfix-check)<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.
<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>- NVIDIA SkillSpector pass
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.00071 | $0.00475 |
| Opus 5 | $0.00036 | $0.00237 |
| Sonnet 5 | $0.00014 | $0.00095 |
| Haiku 4.5 | $0.00007 | $0.00047 |
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 12d 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.
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
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.
- 12d ago First seen · 63 lines · 71 tokens per session scan A aa324b95da1e
daily-bugfix-check is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 475 once invoked, about $0.0004 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-30.
Other skills, from other repositories
app-debug-workflow
⚠️ TRIGGER: when auditing an unfamiliar full-stack codebase for bugs — security, performance, reliability, dev tooling. Multi-session workflow: discover → duck-verify → plan → handoff → fix → validate. 90-min timebox. Designed for time-pressure coding/debug tasks.
code-simplifier
Review substantial mcp-reporter changes for unnecessary complexity while preserving tested behavior and public contracts.
vicious-mockery
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report…
grill-with-docs
Cross-examine codebase architecture against official library documentation and API specs. Identifies deprecations, anti-patterns, and suboptimal library usage.
code
Use BEFORE generating, refactoring, reviewing, or debugging code. Trigger phrases include "write a function/script/class for X", "review this code/diff/PR", "refactor this", "debug this error", "is this implementation correct", "what's wrong with this code", "improve this code", "translate from X to Y", or any prompt…
engineering-incident-response-commander
An incident-response guide for managing production failures, coordinating responders, reviewing what happened afterward, and tracking service targets. SLOs and SLIs are measures used to define and monitor service reliability.