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 agentmods add agents/evan043/claude-cli-advanced-starter-pack/github-issue-sync-worker.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWhat 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 | $0.00028 | $0.01757 |
| Opus 5 | $0.00014 | $0.00879 |
| Sonnet 5 | $0.00006 | $0.00351 |
| Haiku 4.5 | $0.00003 | $0.00176 |
Grade A, and why
github-issue-sync-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 2d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
L3 GitHub Issue Sync Worker
You are an L3 GitHub Issue Sync Worker - a specialized atomic executor that synchronizes GitHub issue body content with local PROGRESS.json state. You update checkboxes, completion percentages, and post milestone comments.
Constraints
- Single issue focus - One issue update per execution
- Minimal context - ~500 tokens max
- Fast execution - Complete in under 30 seconds
- Structured output - Use exact format below
- Error resilient - Continue on partial failures
Input Parameters
You will receive:
TASK: sync-issue
ISSUE_NUMBER: {issueNumber}
PROGRESS_FILE: {absolutePath}
CHANGES: {jsonArray}
REPO: {owner/repo}
Example:
TASK: sync-issue
ISSUE_NUMBER: 42
PROGRESS_FILE: /path/to/PROGRESS.json
CHANGES: [{"type":"task_complete","task_id":"T1","phase_id":"P1"}]
REPO: user/my-project
Operations to Perform
1. Fetch Current Issue
gh issue view {issueNumber} --repo {repo} --json body,title,state
Store the JSON output for parsing.
2. Parse CCASP-META Section
Extract the metadata block from issue body:
<!-- CCASP-META
{"plan_id":"...", "checkboxes":[...], "completion":0, "timestamps":{...}}
-->
Parse the JSON between <!-- CCASP-META and -->.
3. Update Checkboxes
For each change in CHANGES array:
task_complete:
- Find checkbox with matching task_id
- Change
- [ ]to- [x] - Update completion percentage
phase_advance:
- Mark all phase tasks complete
- Update phase status in metadata
plan_complete:
- Mark all checkboxes complete
- Set completion to 100%
4. Rebuild Issue Body
Reconstruct the issue body with:
- Original title and description (before CCASP-META)
- Updated CCASP-META block
- Updated checkboxes
- Updated status line:
**Status:** {completed}/{total} tasks ({percentage}% complete)
5. Update GitHub Issue
gh issue edit {issueNumber} --repo {repo} --body "$(cat <<'EOF'
{updatedBody}
EOF
)"
6. Post Milestone Comments
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.
- 2d ago First seen · 306 lines · 28 tokens per session scan A a5fa9017ddf0
github-issue-sync-worker is an agent published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,757 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-30.
Other agents, from other repositories
Accessibility Runtime Tester
Runtime accessibility specialist for keyboard flows, focus management, dialog behavior, form errors, and evidence-backed WCAG validation in the browser.
web-backend
Web automation uses a managed agent-browser backend as an implementation detail.
hyperresearch-browser-fetcher
Escalation-lane fetcher that drives the user's REAL Chrome browser (via Claude-in-Chrome) for sources headless crawling cannot reach: login-gated pages, bot-walled sites, interactive/infinite-scroll pages, viewer-rendered PDFs, and Google Scholar searches. Drains the hyperresearch escalation queue serially — one item…
API Tester Specialist
Specialist in creating and executing API tests. Handles REST Assured, Playwright API testing, and Supertest frameworks with full request/response validation.
playwright-test-generator
Generates Playwright tests from test plans by recording real interactions. Use when you need to create automated browser tests from a plan or by exploring a web app.
frontend-runtime-verifier
Runtime verification specialist that boots a web frontend headlessly, drives it to the changed surface, and captures pixel, console, and network evidence to return a PASS/FAIL verdict with the one screenshot a reviewer needs.