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 anton-abyzov/specweave --skill syncgit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/anton-abyzov/specweave/sync)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/sync"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/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.00000 | $0.00758 |
| Opus 5 | $0.00000 | $0.00379 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
sync scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Everything goes through the CLI. Never call `gh`, `curl`, or a provider REST API How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw:sync — external tracker sync
Everything goes through the CLI. Never call gh, curl, or a provider REST API
directly: the CLI owns token resolution, the rate budget, duplicate detection and
the bidirectional links.
Commands
| Intent | Command |
|---|---|
| Push local progress to issues | specweave sync push [increment-id] |
| Preview a push | specweave sync push <id> --dry-run |
| Push to one provider | specweave sync push <id> --provider github |
| Fix stale/duplicate milestones first | specweave sync push <id> --reconcile |
| Report external changes | specweave sync pull [--since 7] |
| Import issues as increments | specweave sync pull --create-increments |
| Tokens, health, retry queue, gaps | specweave sync status [--json] |
| Connect a provider | specweave sync setup [--provider github] |
| Validate an existing config | specweave sync setup --validate |
sync push runs tasks.md → spec.md ACs → living docs → provider write, then
drains the retry queue through the same entry point. Exit code of
sync status is 1 when anything needs attention; --json prints one parsable
report (providers, github, health, resilience, gaps, hasIssues).
Not sync: specweave doctor --fix-status repairs metadata.json ↔ spec.md status
desyncs, and specweave sync-living-docs regenerates internal living docs.
Providers
Read the provider from .specweave/config.json (sync.github / sync.profiles);
never guess. GitHub is the first-class path. Jira and Azure DevOps are
community-maintained: push and close work, nothing else is guaranteed — say so
before promising Jira/ADO behaviour.
Tokens resolve in one documented order: .specweave/config.json → process.env
(GITHUB_TOKEN, then GH_TOKEN) → project .env → gh auth token.
sync status prints which layer and which account won. A 404 on write means the
token's account has no write access to owner/repo — fix the token, do not retry.
Concept mapping tables: plugins/specweave/reference/{github,jira,ado}/*-specweave-mapping.md.
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.
- 3d ago First seen · 64 lines · 0 tokens per session scan A fc5b06b02351
sync is a skill published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 758 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
aigon-next
Suggest the most likely next workflow action based on current context.
gh
You have access to gh (GitHub CLI) for repository and project management.
aigon-feature-reset
Reset feature - remove worktrees, branches, state, and return lifecycle to backlog.
creating-issues-and-pull-requests
Use when creating GitHub pull requests or issues with template compliance. Triggers: 'create a PR', 'open a pull request', 'file an issue', 'create issue'. Also invoked by finishing-a-development-branch. NOT for: deciding whether to merge or PR (use finishing-a-development-branch).
genie-orca-work
Coordinator loop for an approved wish on Orca — one Run per wish, one Task per group, supervised workers in child worktrees, review→fix loops, Linear written only at gate transitions. genie v6 'corpo leve': genie owns the documents and this protocol; Orca owns dispatch state; Linear owns status; brain owns preferences.
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.