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 ArabelaTso/Skills-4-SE --skill code-repair-generation-combogit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/code-repair-generation-combo)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/code-repair-generation-combo"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-repair-generation-combo/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/arabelatso/skills-4-se/code-repair-generation-combo"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-repair-generation-combo.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.00119 | $0.01169 |
| Opus 5.5 | $0.00048 | $0.00468 |
| Sonnet 5.5 | $0.00024 | $0.00234 |
| Haiku 4.5 | $0.00012 | $0.00117 |
Grade A, and why
code-repair-generation-combo 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 1mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Repair + Generation Combo
Automatically diagnose and repair buggy code while generating comprehensive tests to verify correctness and prevent regressions.
Workflow
Follow this systematic approach for bug fixing and test generation:
1. Understand the Bug
Read the buggy code - Use Read tool to examine the problematic code thoroughly.
Analyze the specification - Understand expected behavior from:
- Natural language description from user
- Existing failing test cases
- Input/output examples provided
- Error messages or stack traces
Identify the scope - Determine if the bug affects:
- A single function
- Multiple related functions
- An entire module
- Cross-module interactions
2. Diagnose the Root Cause
Trace the logic - Walk through the code execution mentally or with examples.
Identify the bug type:
- Logic error: Code runs but produces wrong results (off-by-one, wrong operator, incorrect condition)
- Runtime error: Code crashes or throws exceptions (null pointer, array out of bounds, type mismatch)
Pinpoint the exact location - Identify the specific lines causing the issue.
Understand side effects - Check if the bug affects other parts of the codebase.
3. Fix the Code
Apply minimal changes - Fix only what's broken, preserve existing functionality.
Use Edit tool - Make precise changes to the buggy code.
Verify the fix logic - Ensure the fix addresses the root cause, not just symptoms.
Preserve code style - Match existing formatting, naming conventions, and patterns.
4. Generate Comprehensive Tests
Load testing patterns - Read the appropriate reference file:
- Python:
references/python-testing.md - Java:
references/java-testing.md - C++:
references/cpp-testing.md
Create test cases covering:
- Normal cases: Typical valid inputs
- Edge cases: Boundary values, empty inputs, single elements
- Error cases: Invalid inputs, null values, exceptions
- Regression cases: Specific inputs that triggered the original bug
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 149 lines · 119 tokens per session scan A 34483783ee12
code-repair-generation-combo is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (259 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 1,169 once invoked, about $0.0005 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.
Other skills, from other repositories
ponytail-dev
Use to implement or review software with minimal code and proportional checks.
absolute-deflake
Flaky test fixes: detect nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnose the root cause, fix it — never retry/skip/sleep — and verify across many randomized runs. Triggers on "absolute deflake", "fix flaky tests", "CI is flaky", "this test fails randomly/intermittently".
debug
Investigate a bug to its root cause systematically — reproduce, trace the data flow, test one hypothesis at a time — then fix it with a regression test. Use when something is broken and the user has a symptom or error message to chase down.
skill-code-quality
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
skill-incident-management
Incident response, postmortem facilitation, root cause analysis (RCA), blameless culture, incident timeline documentation, and incident classification. Use when responding to production incidents, writing incident reports, facilitating postmortems, or improving incident response processes.