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-syncgit 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-sync)<a href="https://agentmods.dev/skills/sw-in-beta/simon-skills/simon-sync"><img src="https://agentmods.dev/badge/skills/sw-in-beta/simon-skills/simon-sync.svg" alt="Measured on agentmods" 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.00112 | $0.01919 |
| Opus 5 | $0.00056 | $0.00959 |
| Sonnet 5 | $0.00022 | $0.00384 |
| Haiku 4.5 | $0.00011 | $0.00192 |
Grade A, and why
simon-sync 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 7d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
simon-sync
simon-* 스킬 패밀리의 변경사항을 ~/simon-skills 오픈소스 레포에 동기화하고, README를 전문가 수준으로 업데이트한 뒤, 자동 커밋 & 푸시하는 스킬.
트리거
- 자동: PostToolUse 훅이
~/.claude/skills/simon-*파일 변경을 감지하면 마커 파일 생성 → Stop 훅이 이 스킬 실행 지시 (10분 쿨다운 적용) - 수동:
/simon-sync명령으로 직접 호출
자동 트리거 시 (Stop 훅에 의한 호출)
메인 세션의 컨텍스트를 보호하기 위해, 최소한의 작업만 수행하고 나머지는 백그라운드 Agent에 위임한다.
메인 세션에서 수행할 작업 (3단계로 즉시 완료):
-
마커 삭제 + 쿨다운 타임스탬프 갱신:
rm -f /tmp/.simon-skill-sync-needed && touch /tmp/.simon-skill-last-sync -
백그라운드 Agent를 spawn (
run_in_background: true)하여 아래 "동기화 절차" 전체를 위임. Agent prompt에 동기화 절차 섹션 내용을 포함시킨다. -
사용자에게 "동기화를 백그라운드에서 시작했습니다"라고 한 줄 안내 후 즉시 턴 종료.
절대로 메인 세션에서 동기화 절차를 직접 실행하지 않는다.
수동 호출 시
/simon-sync로 직접 호출된 경우에도 백그라운드 Agent로 실행한다. 동일한 3단계를 따른다.
동기화 절차
이 섹션은 백그라운드 Agent가 수행하는 작업이다.
Step 1: 동기화 대상 파악
동기화 대상 스킬 목록 (이 목록에 없는 스킬은 동기화하지 않는다):
simonsimon-auto-boostsimon-boostsimon-boost-capturesimon-boost-reviewsimon-ci-fixsimon-grindsimon-pmsimon-reportsimon-code-reviewsimon-sessionssimon-companysimon-presenter
제외 대상:
simon-sync(이 스킬 자체 — 메타 스킬이므로 레포에 포함하지 않음)*-workspace/디렉토리 (로컬 eval 데이터)evals/디렉토리 (로컬 eval 데이터)~/.claude/skills/simon/workflow/(레포의workflow/에서 복사된 것)~/.claude/skills/simon/install.sh(레포의install.sh에서 복사된 것)
Step 2: 파일 동기화
각 대상 스킬에 대해 rsync로 동기화한다:
rsync -av --delete \
--exclude='evals/' \
--exclude='*-workspace/' \
~/.claude/skills/<skill-name>/ ~/simon-skills/skills/<skill-name>/
simon 스킬은 추가 제외 필요:
rsync -av --delete \
--exclude='evals/' \
--exclude='*-workspace/' \
--exclude='workflow/' \
--exclude='install.sh' \
~/.claude/skills/simon/ ~/simon-skills/skills/simon/
Step 2.5: Secret Scanning (동기화 전 시크릿 검사)
rsync 완료 후, git commit 전에 동기화된 스킬 파일들의 내용을 검사하여 API 키, 토큰, 패스워드 등 민감 정보가 포함되지 않았는지 확인한다. 퍼블릭 레포에 시크릿이 푸시되는 것을 방지하기 위한 필수 단계.
~/simon-skills/hooks/secret-scan.sh 스크립트를 --dir 모드로 실행:
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.
- 7d ago First seen · 172 lines · 112 tokens per session scan A 966fb363bb7f
simon-sync is a skill published in the GitHub repository SW-in-beta/simon-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 1,919 once invoked, about $0.0006 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".