agentmods.dev

marker-client-report

marker-client-report is a skill for Claude Code, Codex from marker-io/mcp-skills. It costs 71 tokens per session (1,269 once invoked), scanned A, original, MIT.

A read-only report writer that turns completed Marker.io website work into a client-facing weekly or monthly summary. It groups the work by website page and uses plain language.

In plain words
What is it for?
Use it to summarize what was shipped or fixed during a chosen period and prepare a report for a website client.
Why use it?
It saves time when preparing client updates from issue data. It presents completed work as a clear recap instead of a technical backlog.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 7repo 5mo ago A scan 71 tokens original MIT

Good fit Use it to summarize what was shipped or fixed during a chosen period and prepare a report for a website client.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marker-io/mcp-skills/marker-client-report
View source ↗ marker-io/mcp-skills marker.io
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-client-report
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.

agentmods badge for marker-client-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/marker-io/mcp-skills/marker-client-report/github.svg)](https://agentmods.dev/skills/marker-io/mcp-skills/marker-client-report)
Your own site
<a href="https://agentmods.dev/skills/marker-io/mcp-skills/marker-client-report"><img src="https://agentmods.dev/badge/skills/marker-io/mcp-skills/marker-client-report/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.

agentmods 80×15 button for marker-client-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/marker-io/mcp-skills/marker-client-report"><img src="https://agentmods.dev/badge/skills/marker-io/mcp-skills/marker-client-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,269 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.01269
Opus 5.5 $0.00028 $0.00508
Sonnet 5.5 $0.00014 $0.00254
Haiku 4.5 $0.00007 $0.00127

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

Security

Grade A, and why

marker-client-report 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-client-report/SKILL.md · 88 lines

How it starts

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

marker-client-report

Produce a polished, client-facing recap of what an agency completed on a website over a week or month, straight from Marker.io — grouped by page, written in plain language, ready to paste into an email or send as-is. Read-only.

When to use

"Write the weekly report for <client>", "what did we ship for <project> this month", "monthly recap for the <site> work", "client status update from Marker". For analyzing recurring patterns rather than reporting a period's work, use marker-insights; for triaging the open backlog, use marker-triage.

Inputs to confirm

  • Which project (one client / site is usually one project; resolve per the operating rules).
  • The window: default the last 7 days, or "last month" / last 30 days / an explicit date range.
  • Whether to include sections beyond completed work: in-progress now, and newly reported this period. Default: completed only.

Steps

  1. Resolve the project and read project_get for its name and websiteUrls (the report header and the page mapping).
  2. Decide which statuses count as completed — Resolved and Closed by default. Statuses are project-specific and can be renamed, so don't assume a customized board uses the English defaults: confirm which are in use by probing issues_list with each status value, and if it is unclear which statuses mean "done", show the candidates and ask.
  3. Pull issues with issues_list, paginating limit/offset fully. Keep fields lean: markerId, title, status, url, createdAt, updatedAt. The MCP has no date filter, so window client-side: an item counts as completed this period when its status is one of the completed states and its updatedAt falls in the window.
  4. Classify each completed item as a content update (typo, copy, wrong number or fact, image, link, layout) or a fix (functional bug). Marker does not expose an issue's type to read, so infer it from the title and page URL; open issue_get / issue_get_screenshot only when the title is too thin to describe in client terms.
  5. Group by page (from the URL relative to websiteUrls), and within a page by content vs fix.
  6. Write the report (see Output). Translate internal titles into client language: "Fix typo in intro paragraph" becomes "Corrected a typo in the Solutions page intro". Drop Marker jargon, statuses, and IDs from the client-facing copy.

Read the full file on GitHub · 88 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. 2mo ago First seen · 88 lines · 71 tokens per session scan A 8a8c854419d4

Subscribe to this mod's changes

marker-client-report is a skill published in the GitHub repository marker-io/mcp-skills (7 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,269 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 CodeProject managementWriting and docsagent-skillsantigravitycursormcpskills
Related

marker-client-report compared with skills from other repositories

marker-client-report next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
marker-client-reportmarker-io/mcp-skillsSkill75mo agoMITA71Claude Code, Codex
test-driven-developmentaddyosmani/agent-skillsSkill114k5d agoMITA92Claude Code
context-engineeringaddyosmani/agent-skillsSkill114k5d agoMITA43Claude Code
doubt-driven-developmentaddyosmani/agent-skillsSkill114k5d agoMITA96Claude Code
git-workflow-and-versioningaddyosmani/agent-skillsSkill114k5d agoMITA131Claude Code
observability-and-instrumentationaddyosmani/agent-skillsSkill114k5d agoMITA66Claude Code
performance-optimizationaddyosmani/agent-skillsSkill114k5d agoMITA59Claude Code