github-push

A command that sends local progress for a SpecWeave increment to its linked GitHub issue, similar to sending local commits with git push.

In plain words
What is it for?
Use it to update the current or a specified increment, provided the project allows changes to external GitHub items.
Why use it?
It keeps GitHub task checklists, progress comments, labels, and completion state aligned with the local tasks.md file.

Command

Install

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.

agentmods
npx agentmods add commands/anton-abyzov/specweave/github-push
Clone the repo
git clone --depth 1 https://github.com/anton-abyzov/specweave
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00777
Opus 5 $0.00010 $0.00388
Sonnet 5 $0.00004 $0.00155
Haiku 4.5 $0.00002 $0.00078

Measured 2d ago against content hash ebc244f367e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-push 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.

plugins/specweave/commands/github-push.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Push Command

Usage: sw-github:push [increment-id]

Purpose: Push local progress to GitHub Issues (like git push)


Quick Start

# Push current/active increment
sw-github:push

# Push specific increment
sw-github:push 0005

What Gets Pushed

Field Source
Task Checklist Updated from tasks.md completion
Comment Auto-generated progress update
Labels Status labels updated
State Closed if 100% complete

Command Behavior

When user runs this command:

1. Check Permission Gate

const config = JSON.parse(await fs.readFile('.specweave/config.json', 'utf-8'));
const canUpdateExternal = config?.sync?.settings?.canUpdateExternalItems ?? false;

if (!canUpdateExternal) {
  console.log(`
Permission Denied: GitHub writes disabled

To enable: Set sync.settings.canUpdateExternalItems = true

Or use read-only: sw-github:pull ${incrementId}
`);
  return;
}

2. Calculate Progress

const tasksContent = await fs.readFile(
  `.specweave/increments/${incrementId}/tasks.md`, 'utf-8'
);

const totalTasks = (tasksContent.match(/### T-\d+/g) || []).length;
const completedTasks = (tasksContent.match(/\[x\] completed/gi) || []).length;
const percentage = Math.round((completedTasks / totalTasks) * 100);

3. Invoke Push Sync

Use Skill tool: Skill({ skill: "sw-github:github-sync", args: "Push progress to GitHub for increment {increment-id}.

Issue: #{issueNumber}
Progress: {completedTasks}/{totalTasks} ({percentage}%)

Steps:
1. Update issue body task checklist
2. Add progress comment
3. Update labels if needed
4. Close issue if 100% complete (if canUpdateStatus)
5. Update sync timestamp"

4. Display Result

Pushed to GitHub

Issue: #123
Repository: owner/repo

Progress: 6/10 tasks (60%)

Updates:
  Task checklist: 6/10 checked
  Comment: Progress update posted
  Labels: +in-progress

URL: https://github.com/owner/repo/issues/123

Read the full file on GitHub · 152 lines

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.

  1. 2d ago First seen · 152 lines · 19 tokens per session scan A ebc244f367e7

Subscribe to this mod's changes

github-push is a command published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 777 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.