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 Zhang-Henry/CoEvoSkills --skill evo-fjsp-repairgit clone --depth 1 https://github.com/Zhang-Henry/CoEvoSkillsWrote 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/zhang-henry/coevoskills/evo-fjsp-repair)<a href="https://agentmods.dev/skills/zhang-henry/coevoskills/evo-fjsp-repair"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-fjsp-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/zhang-henry/coevoskills/evo-fjsp-repair"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-fjsp-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.00051 | $0.00428 |
| Opus 5 | $0.00026 | $0.00214 |
| Sonnet 5 | $0.00010 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
evo-fjsp-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 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
FJSP Baseline Repair Skill
Overview
Repairs Flexible Job-Shop Scheduling baseline schedules that have downtime violations. Produces a feasible schedule with minimized makespan while respecting:
- Machine eligibility and correct durations
- Intra-job precedence ordering
- No machine overlap (half-open intervals)
- Zero downtime violations
- Right-shift-only constraint
- Freeze policy for early operations
- Machine change and L1 shift budgets
- Makespan ratio guard
Scripts
scripts/parser.py- Parse instance, downtime, policy, baseline filesscripts/constraints.py- Validation functions for all constraint typesscripts/solver.py- Greedy repair algorithms with multiple strategiesscripts/writer.py- Write solution.json and schedule.csv outputsscripts/entrypoint.py- End-to-end pipeline: parse, repair, validate, write
Usage
import sys
sys.path.insert(0, '/app/environment/skills/evo-fjsp-repair/scripts')
from entrypoint import run, validate
# Run full pipeline
result = run('/app/data', '/app/output')
# Validate outputs
valid = validate('/app/output', '/app/data')
if not valid:
print("Schedule has issues - check output")
Algorithm
- Parse all input files
- Identify frozen operations (baseline start < freeze_until)
- Identify frozen ops with downtime violations (must be reassigned)
- Process operations in precedence-aware order (op index asc, baseline start asc)
- For each operation, find earliest feasible start on each eligible machine
- Select assignment minimizing end time while staying within policy budgets
- Try multiple strategies (minimize end time vs minimize duration) and pick best
- Write outputs and validate
What ships with it
5 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.
- 12d ago First seen · 52 lines · 51 tokens per session scan A 9027fd85fdec
evo-fjsp-repair is a skill published in the GitHub repository Zhang-Henry/CoEvoSkills (66 stars, last pushed 22d ago), licensed Apache-2.0. It adds 51 tokens to every session and 428 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…