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 SW-in-beta/simon-skills --skill simon-ci-fixgit clone --depth 1 https://github.com/SW-in-beta/simon-skillsWrote 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/sw-in-beta/simon-skills/simon-ci-fix)<a href="https://agentmods.dev/skills/sw-in-beta/simon-skills/simon-ci-fix"><img src="https://agentmods.dev/badge/skills/sw-in-beta/simon-skills/simon-ci-fix/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/sw-in-beta/simon-skills/simon-ci-fix"><img src="https://agentmods.dev/badge/skills/sw-in-beta/simon-skills/simon-ci-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00139 | $0.03024 |
| Opus 5 | $0.00069 | $0.01512 |
| Sonnet 5 | $0.00028 | $0.00605 |
| Haiku 4.5 | $0.00014 | $0.00302 |
Grade A, and why
simon-ci-fix 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.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
simon-ci-fix
PR의 CI 체크를 모니터링하고, 실패 시 자동으로 수정하는 스킬. 에러 유형별 전문 복구 전략으로 최대 5회 사이클을 반복하여 모든 체크가 통과할 때까지 수정한다.
Mode Detection
- 입력 파라미터 확인: PR 번호, 브랜치명, SESSION_DIR이 전달되었는지 확인
- DELEGATED 모드: PR 번호가 전달됨 (simon-code-review 또는 다른 스킬에서 호출)
- STANDALONE 모드: PR 번호 미전달 → 자동 감지
PR 없으면 사용자에게 안내: "현재 브랜치에 PR이 없습니다. PR 번호를 알려주세요."gh pr view --json number,url --jq '{number: .number, url: .url}'
Shared Protocols:
~/.claude/skills/_shared/preamble.md읽기 — Session Isolation, Error Resilience, Forbidden Rules 공통 프로토콜 포함.
STANDALONE SESSION_DIR 설정
STANDALONE 모드에서는 preamble의 Session Isolation Protocol에 따라 SESSION_DIR을 직접 결정한다.
Workflow
[Mode Detection] → PR 번호 확보
↓
Step 1: CI 상태 확인 ←──────────────┐
↓ │
모두 통과? ── Yes → 결과 보고 │
│ │
No │
↓ │
Step 2: 실패 로그 수집 │
↓ │
Step 3: 에러 분류 │
↓ │
ENV만? ── Yes → 결과 보고 (수정불가) │
│ │
No │
↓ │
Step 4: 진단 + 수정 │
↓ │
[GATE] 구조적 변경? → 사용자 확인 │
↓ │
Step 5: 커밋 + 푸시 ─── cycle < 5 ───┘
│
cycle >= 5
↓
결과 보고 (미해결 실패 포함)
Step 1: CI 상태 확인
CI 체크 상태를 확인한다. push 직후에는 CI가 아직 시작되지 않았을 수 있으므로 대기 로직을 포함한다.
CHECKS=$(gh pr checks {pr_number} 2>&1)
체크 상태 해석:
- 모든 체크 pass → SUCCESS → 결과 보고
- 실패한 체크 존재 → Step 2
- 체크가 pending → 30초 대기 후 재확인 (최대 10회, 5분)
- 체크가 하나도 등록되지 않음 → 60초 대기 후 재확인 (최대 5회, CI 트리거 대기)
진행 상황 기록:
echo "## Cycle {N} - $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> {SESSION_DIR}/memory/ci-fix-progress.md
echo "Status: CHECKING" >> {SESSION_DIR}/memory/ci-fix-progress.md
Step 2: 실패 로그 수집
실패한 각 체크의 상세 로그를 수집한다.
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 · 263 lines · 139 tokens per session scan A cf6a67402a72
simon-ci-fix is a skill published in the GitHub repository SW-in-beta/simon-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 3,024 once invoked, about $0.0007 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-31.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.