A synchronization rule for keeping Marker.io website reports and an issue tracker such as GitHub, Linear, or Jira consistent. It moves diagnostic details and status changes between the two systems.

Use it to import new reports, enrich tracker tickets, update resolved work, or find status mismatches between Marker.io and the connected tracker.

It prevents a report from being closed in one system while remaining open in the other. It also gives tracker tickets useful evidence, such as screenshots, browser details, and error information.

marker-sync — Skill for Claude Code and Codex by marker-io/mcp-skills

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.

Any agent

npx skills add marker-io/mcp-skills --skill marker-sync

Clone the repo

git clone --depth 1 https://github.com/marker-io/mcp-skills

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/marker-io/mcp-skills/marker-sync/github.svg)](https://agentmods.dev/skills/marker-io/mcp-skills/marker-sync)

Your own site

<a href="https://agentmods.dev/skills/marker-io/mcp-skills/marker-sync"><img src="https://agentmods.dev/badge/skills/marker-io/mcp-skills/marker-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/marker-io/mcp-skills/marker-sync"><img src="https://agentmods.dev/badge/skills/marker-io/mcp-skills/marker-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 890 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00064	$0.00890
Opus 5.5	$0.00026	$0.00356
Sonnet 5.5	$0.00013	$0.00178
Haiku 4.5	$0.00006	$0.00089

Measured 2mo ago against content hash 1dd275e0fbaa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

marker-sync 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 2mo 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.

claude/skills/marker-sync/SKILL.md · 66 lines

How it starts

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

marker-sync

Keep Marker.io and an external tracker (GitHub Issues, Linear, Jira) consistent: full diagnostic context flows into the tracker, resolution flows back to Marker. Eliminates the "closed in the tracker, still open in Marker.io" mismatch.

When to use

"Pull new marker issues into <tracker>", "enrich these tickets with marker context", "mark the done ones ready to test in github and resolved in marker", "are marker and linear out of sync".

Prerequisites

A connected tracker. Use whatever the user has: GitHub via the gh CLI, Linear via mcp__linear__*, Jira via its MCP/CLI. If none is connected, say so and stop.

Matching issues across systems

Match a Marker.io issue to its tracker item by, in order: an explicit Marker link/ID in the tracker item, the issue URL, then a close title match. When unsure, list the candidate pairs and ask.

Steps

Pull new/updated Marker.io issues (issues_list, recent window). Pull the corresponding tracker items in one pass.
Enrich thin tracker items: for any tracker ticket missing diagnostic context, add the Marker screenshot link, console errors, failing network requests, and browser/OS from issue_get_context (plus drill-downs). Propose the edit before writing to the tracker.
Reconcile status both ways. Build a table of every pair and its two statuses. Flag mismatches (resolved on one side, open on the other).
On close: when a fix has landed, set the tracker state (e.g. "Ready to Test") and the Marker.io status to its resolved equivalent (issue_update_status, discovered via project_get), and document the root cause + fix as a comment on both sides (comment_create on Marker).

Gating

Every write (tracker edits, Marker status changes, comments) is proposed as a table first and applied only after confirmation. Never close an issue on one side without updating the other.

Operating rules

This skill drives the Marker.io MCP. Read tools: projects_list, project_get, project_list_users, list_issue_types, issues_list, issue_get, issue_get_context, issue_get_screenshot, issue_get_attachments, issue_get_console_log, issue_get_network_request. Write tools: issue_update_status, issue_update_assignee, issue_update_priority, issue_update_type, comment_create.

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

2mo ago First seen · 66 lines · 64 tokens per session scan A 1dd275e0fbaa

Subscribe to this mod's changes

marker-sync is a skill published in the GitHub repository marker-io/mcp-skills (7 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 890 once invoked, about $0.0003 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-31.

Claude Code Project management agent-skills antigravity cursor mcp skills

marker-sync next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
marker-syncmarker-io/mcp-skills	Skill	7	5mo ago	MIT	A	64	Claude Code, Codex
test-driven-developmentaddyosmani/agent-skills	Skill	114k	5d ago	MIT	A	92	Claude Code
context-engineeringaddyosmani/agent-skills	Skill	114k	5d ago	MIT	A	43	Claude Code
doubt-driven-developmentaddyosmani/agent-skills	Skill	114k	5d ago	MIT	A	96	Claude Code
git-workflow-and-versioningaddyosmani/agent-skills	Skill	114k	5d ago	MIT	A	131	Claude Code
observability-and-instrumentationaddyosmani/agent-skills	Skill	114k	5d ago	MIT	A	66	Claude Code
performance-optimizationaddyosmani/agent-skills	Skill	114k	5d ago	MIT	A	59	Claude Code

marker-sync

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

marker-sync

When to use

Prerequisites

Matching issues across systems

Steps

Gating

Operating rules

What this file has done since we first saw it

marker-sync compared with skills from other repositories