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 phj128/autoworker --skill sync-docsgit clone --depth 1 https://github.com/phj128/autoworkerWrote 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/phj128/autoworker/sync-docs)<a href="https://agentmods.dev/skills/phj128/autoworker/sync-docs"><img src="https://agentmods.dev/badge/skills/phj128/autoworker/sync-docs/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/phj128/autoworker/sync-docs"><img src="https://agentmods.dev/badge/skills/phj128/autoworker/sync-docs.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.00040 | $0.01880 |
| Opus 5.5 | $0.00016 | $0.00752 |
| Sonnet 5.5 | $0.00008 | $0.00376 |
| Haiku 4.5 | $0.00004 | $0.00188 |
Grade A, and why
sync-docs 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 1mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autoworker:sync-docs — Sync Tracking Documents
Based on work results and discoveries in the current conversation, update all tracking documents.
Input
Optional argument: $ARGUMENTS
- No argument: Sync only (check off items, record progress, add findings, audit claude_docs)
park: Sync + pause current subtask (setstatus: paused) + clear plan file. For "task still in progress (e.g., training) but need to switch to something else"archive: Sync + archive completed subtask (move to claude_docs/subtask/) + clear plan file. For "task fully complete"
Execution Flow
1. Scan Current State
Find tracking files and document system in the project root:
Top-level tracking files:
subtask_*.md— current in-progress subtasksprogress.md— progress logfindings.md— core discoveriestask_plan.md— task planning- Project-level
CLAUDE.md— project rules and technical info README.md— project intro (for humans)
Progressive disclosure documents:
claude_docs/reference/*.md— detailed documents referenced from CLAUDE.md- Subdirectory
CLAUDE.md— index files for each module
Read each existing file to understand current recorded state.
2. Compare Against Conversation Content
Review work completed in this conversation, determine updates needed item by item:
| File | Update condition | Update content |
|---|---|---|
subtask_*.md |
Steps were completed | Check off [x], record progress, add verification results |
progress.md |
Task completed or progressed | Update task item status, add result summary |
findings.md |
New conclusions or counter-intuitive behaviors discovered | Add new section or update existing section |
task_plan.md |
Task completed/progressed, or plan changed | Read subtask's "task_plan positioning → corresponding Phase" field, locate and check off [x] in task_plan.md with completion timestamp; match by content when no positioning field; update future steps if plan changed |
CLAUDE.md |
Reusable patterns or lessons learned discovered | Add to appropriate section (don't duplicate existing content) |
claude_docs/reference/*.md |
Findings in this conversation belong to an existing reference topic | Update corresponding reference document |
Subdirectory CLAUDE.md |
Changed code structure/files in a module | Update corresponding subdirectory file index |
README.md |
Added feature or changed usage/installation | Sync update (user-perceivable changes) |
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.
- 1mo ago First seen · 158 lines · 40 tokens per session scan A 166e20f9e9a6
sync-docs is a skill published in the GitHub repository phj128/autoworker (18 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 1,880 once invoked, about $0.0002 per session on Opus 5.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
flow-next-flow
Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-land
Resolve feedback and CI for one named pull request, then merge when authorized and ready. Emits LANDVERDICT. Use when asked to land a pull request.