Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/getklaim/claude-auto-contextnpx agentmods add skills/getklaim/claude-auto-context/run-workerWrote 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/getklaim/claude-auto-context/run-worker)<a href="https://agentmods.dev/skills/getklaim/claude-auto-context/run-worker"><img src="https://agentmods.dev/badge/skills/getklaim/claude-auto-context/run-worker.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.00024 | $0.00487 |
| Opus 5 | $0.00012 | $0.00244 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
run-worker 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 6d 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
Run Worker
Auto Context 워커를 수동 실행하거나 상태를 확인한다.
Current Status
- Lock file: !
LOCK=".claude-auto-context/worker.lock"; if [ -f "$LOCK" ]; then PID=$(cat "$LOCK"); if kill -0 "$PID" 2>/dev/null; then echo "RUNNING (pid=$PID)"; else echo "STALE LOCK (pid=$PID, not alive)"; fi; else echo "NOT RUNNING"; fi - Pending events: !
sqlite3 .claude-auto-context/db/claude-auto-context.db "SELECT count(*) FROM raw_events WHERE status='pending'" 2>/dev/null || echo "DB not found" - Recent log:
!tail -5 .claude-auto-context/db/worker.log 2>/dev/null || echo "No log file"
Procedure
Arguments: $ARGUMENTS
status— 위 Current Status 섹션 정보를 보여주고 끝logs—tail -30 .claude-auto-context/db/worker.log실행하여 최근 로그 출력force— 강제 재시작: a. Lock file에서 PID 읽어서kill $PID실행 b. Lock file 삭제:rm -f .claude-auto-context/worker.lockc.scripts/worker-launcher.sh실행 (현재 프로젝트 디렉토리를 인자로 전달) d. 2초 후 lock file 확인하여 시작 여부 보고- 인자 없음 — 스마트 실행:
a. 워커가 이미 RUNNING이면 상태만 보여줌
b. NOT RUNNING 또는 STALE LOCK이면
scripts/worker-launcher.sh실행 후 상태 확인
Launch Command
워커 실행 시 반드시 이 명령을 사용:
./scripts/worker-launcher.sh "$(pwd)"
직접 bun .claude-auto-context/worker.mjs를 실행하지 말 것 — launcher가 lock file, 환경변수(CLAUDECODE unset), 로그 리다이렉트를 처리한다.
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.
- 6d ago First seen · 43 lines · 24 tokens per session scan A 98d1bbd85d82
run-worker is a skill published in the GitHub repository getklaim/claude-auto-context (10 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 487 once invoked, about $0.0001 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.