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/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/anton-abyzov/specweave/sync"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00604 |
| Opus 5.5 | $0.00018 | $0.00242 |
| Sonnet 5.5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
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 27d 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.
through the CLI, never `gh`, `curl` or a provider API directly: the CLI owns token How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw-sync: external tracker sync
Sync is opt-in and explicit. Starting, pausing or completing an increment never calls a
tracker; only specweave sync push does (plus close-on-complete, when configured). Go
through the CLI, never gh, curl or a provider API directly: the CLI owns token
resolution, the rate budget, duplicate detection and the links in both directions.
Commands
| Intent | Command |
|---|---|
| Push progress to issues | specweave sync push [increment-id] |
| Preview a push | specweave sync push 0042 --dry-run |
| One provider only | specweave sync push 0042 --provider github |
| Report external changes | specweave sync pull [--since 7] |
| Import issues as increments | specweave sync pull --create-increments |
| Token, account, health, retry queue | specweave sync status [--json] |
| Connect a provider | specweave sync setup [--provider github] |
| Check an existing setup | specweave sync setup --validate |
sync status exits 1 when anything needs attention.
Providers
Read the provider from .specweave/config.json; never guess. GitHub is first-class.
Jira and Azure DevOps are supported and opt-in: push and close are covered, say so
before promising more.
Tokens resolve in one order: config, then GITHUB_TOKEN / GH_TOKEN, then the project
.env, then gh auth token. sync status prints which one won and for which account.
A 404 on write means that account cannot write to the repository: fix the token, do not
retry. Check a token exists without printing it.
Rules
--dry-runfirst when an increment has never synced.- Never edit the issue links in
metadata.jsonby hand; a broken link is fixed withspecweave sync push 0042 --force. - Report
sync statusoutput as it is when it shows problems; do not paraphrase token or permission errors.
Manual path (no CLI)
There is no manual sync. Update the issue yourself and put its URL in spec.md Problem so the next agent can find it.
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.
- 27d ago Changed · -11 lines · +46 tokens per session 3de5e63b7c76
- 1mo ago First seen · 64 lines · 0 tokens per session scan A fc5b06b02351
sync is a skill published in the GitHub repository anton-abyzov/specweave (167 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 604 once invoked, about $0.0002 per session on Opus 5.5. 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
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
Folio Tables
Work with Folio data tables (kind table) through foliotable MCP tools — schema-first, column types, filters, and typical schemas for a risk register, sprint plan, or backlog.
github
GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…