What is push-to-tracker?

A workflow that reads a project plan from phases.yaml and creates matching projects, phase groups, and dependent issues in Linear, GitHub, or Notion. It uses the tracker selected in the project's settings.

Use it to publish a phases.yaml plan to Linear, GitHub, or Notion as organized, linked work items.

It removes the need to copy project phases into an issue tracker by hand and preserves the order in which work depends on other work.

push-to-tracker — Skill for Claude Code and Codex by firatcand: A workflow that reads a project plan from phases.yaml…

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 skills/firatcand/forge/push-to-tracker

Any agent

npx skills add firatcand/forge --skill push-to-tracker

Clone the repo

git clone --depth 1 https://github.com/firatcand/forge

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/firatcand/forge/push-to-tracker.svg)](https://agentmods.dev/skills/firatcand/forge/push-to-tracker)

Your own site

<a href="https://agentmods.dev/skills/firatcand/forge/push-to-tracker"><img src="https://agentmods.dev/badge/skills/firatcand/forge/push-to-tracker.svg" alt="Measured on agentmods" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,082 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.

Model	Per session	Once invoked
Fable 5	$0.00034	$0.01082
Opus 5	$0.00017	$0.00541
Sonnet 5	$0.00007	$0.00216
Haiku 4.5	$0.00003	$0.00108

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

Security

Grade A, and why

push-to-tracker 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 5d 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.

skills/push-to-tracker/SKILL.md · 80 lines

How it starts

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

/push-to-tracker

Delegate to the tracker-syncer subagent. Tracker-agnostic; dispatches per .forge/settings.yaml's tracker.type.

Preconditions

plans/phases.yaml exists
.forge/settings.yaml exists and has a tracker: block (validated by src/schemas/settings.ts::TrackerConfigSchema — discriminated union on type, one of linear|github|notion)
Per-tracker tooling reachable (Linear MCP / gh CLI / ntn CLI)

Step 0 — Resolve tracker

Read .forge/settings.yaml and extract:

tracker.type ∈ {linear, github, notion}
tracker.config (per-type shape: Linear → team_id; GitHub → repo; Notion → database_id)

If .forge/settings.yaml is missing or tracker: is absent, abort:

No tracker configured. Run `forge init` first, or add a `tracker:` block to .forge/settings.yaml.

If tracker.type is unknown, surface the zod schema error verbatim (one of linear|github|notion).

Step 1 — Preflight per tracker

`tracker.type`	Probe	If missing
`linear`	Linear MCP available	Offer `claude mcp add linear --transport http https://mcp.linear.app/mcp` + OAuth + restart, OR the no-MCP fallback (print Linear-import manifest).
`github`	`gh auth status` exits 0	Instruct `gh auth login`.
`notion`	`ntn` CLI installed + authed (probe: `ntn api v1/users/me`; fix: `ntn login`)	Offer the install one-liner from docs/adapters/notion.md; NotionTracker (src/trackers/notion.ts) drives the `ntn` CLI since FORGE-117.

Step 2 — Delegate to `tracker-syncer`

Pass tracker.type, tracker.config, and plans/phases.yaml path. The agent dispatches to the right Tracker adapter (see agents/tracker-syncer.md). Concrete flow:

createProject(phases.project.name, phases.project.description) — Linear Project / GitHub Milestone / Notion Database row.
For each phase (in order), for each task: createIssue({ title, body, forgeTaskId, ownerType, acceptance, dependsOn: [] }). Stage the returned issue.id against the task in memory.
Second pass — for every task with depends_on, call setBlockedBy(task._issueId, blocker._issueId) once per blocker. Two passes because adapters need both issues to exist before relating them.

Read the full file on GitHub · 80 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.

5d ago First seen · 80 lines · 34 tokens per session scan A a317619ff753

Subscribe to this mod's changes

push-to-tracker is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,082 once invoked, about $0.0002 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.

Project management agentic-coding ai-coding-agent claude-code codex compound-engineering spec-driven-development

ospec-change

Create or advance a lightweight OSpec change using the classic fast workflow.

clawplays/ospec · 18 tokens

prospec-knowledge-generate

Generate AI Knowledge - Read raw-scan.md, analyze project structure, autonomously decide module boundaries, and produce Recipe-First module READMEs and index. Triggers: generate knowledge, analyze project, module split, 產生知識, 知識庫, 分析專案, 模組拆分.

benwu95/prospec · 71 tokens

submit-pr

Open a prospec pull request in the house format — push the change's two commits, write the Traditional Chinese body, and link it to its issue. Triggers: submit pr, open pr, 開 PR, 送 PR, 發 PR, pull request, 提交 PR.

benwu95/prospec · 59 tokens

prospec-explore

Explore - Requirement exploration, problem investigation, and solution comparison partner. Triggers: explore, compare, investigate, unsure, clarify, 探索, 比較, 釐清, 調查, 不確定.

benwu95/prospec · 50 tokens

prospec-plan

Plan Implementation - Convert User Story into technical implementation plan (plan.md) and change specification (delta-spec.md). Triggers: plan, architecture, technical plan, 規劃, 架構規劃, 技術規劃.

benwu95/prospec · 53 tokens

prospec-knowledge-update

Incremental Knowledge Update - Parse delta-spec.md to identify affected modules, scan source code, and update module README, index.md, and module-map.yaml incrementally. Triggers: knowledge update, incremental update, sync knowledge, update docs, 更新知識, 增量更新, 同步知識, 更新文件.

benwu95/prospec · 70 tokens