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 model-guided-code-repairgit 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/model-guided-code-repair)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/model-guided-code-repair"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/model-guided-code-repair/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/model-guided-code-repair"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/model-guided-code-repair.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.00097 | $0.01343 |
| Opus 5 | $0.00048 | $0.00672 |
| Sonnet 5 | $0.00019 | $0.00269 |
| Haiku 4.5 | $0.00010 | $0.00134 |
Grade A, and why
model-guided-code-repair 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 9d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model-Guided Code Repair
Overview
This skill enables automatic repair of code that violates temporal properties by analyzing model-checking counterexamples. It reasons about the root cause of violations at the model level, proposes minimal and semantically justified code modifications, and validates repairs through re-verification or test generation.
Repair Workflow
Follow this sequential process when repairing temporal property violations:
1. Analyze Input
Gather and understand three required inputs:
- Program source code: The code containing the violation
- Violated temporal property: The formal specification (LTL, CTL, or natural language description)
- Counterexample trace: The execution path demonstrating the violation
Read all inputs carefully. If the temporal property is in natural language, formalize it first.
2. Understand the Counterexample
Trace through the counterexample step-by-step:
- Identify the sequence of states and transitions
- Map counterexample states to program locations (line numbers, function calls)
- Identify variable values at each step
- Pinpoint the exact moment the property is violated
Output: A clear narrative of the execution path leading to the violation.
3. Identify Root Cause
Analyze why the violation occurs:
- Missing guards: Are conditions missing that should prevent certain transitions?
- Incorrect ordering: Are operations executed in the wrong sequence?
- Race conditions: Are there synchronization issues in concurrent code?
- Missing state updates: Are variables not being updated correctly?
- Incorrect logic: Are conditional expressions wrong?
Output: A precise diagnosis of the model-level cause.
4. Propose Repair Strategy
Design a minimal repair that:
- Directly addresses the root cause
- Preserves intended program behavior
- Minimizes code changes
- Maintains code readability
Common repair strategies:
- Add guards: Insert conditional checks to prevent invalid transitions
- Reorder operations: Adjust execution sequence to satisfy temporal ordering
- Add synchronization: Insert locks, semaphores, or barriers for concurrent code
- Update state management: Fix variable assignments or state transitions
- Strengthen preconditions: Add assertions or input validation
What ships with it
1 file 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.
- 9d ago First seen · 193 lines · 97 tokens per session scan A e30ce3809e5e
model-guided-code-repair is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,343 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
trace
Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
bim-consistency-checker
Check BIM model consistency: naming conventions, parameter completeness, spatial relationships, and data integrity across model elements.
022-root-cause-analysis
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the…