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 marker-io/mcp-skills --skill marker-client-reportgit clone --depth 1 https://github.com/marker-io/mcp-skillsWrote 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/marker-io/mcp-skills/marker-client-report)<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.
<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>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.00071 | $0.01269 |
| Opus 5 | $0.00036 | $0.00634 |
| Sonnet 5 | $0.00014 | $0.00254 |
| Haiku 4.5 | $0.00007 | $0.00127 |
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 12d 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.
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
- Resolve the project and read
project_getfor its name andwebsiteUrls(the report header and the page mapping). - Decide which statuses count as completed —
ResolvedandClosedby 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 probingissues_listwith eachstatusvalue, and if it is unclear which statuses mean "done", show the candidates and ask. - Pull issues with
issues_list, paginatinglimit/offsetfully. 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 itsupdatedAtfalls in the window. - 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_screenshotonly when the title is too thin to describe in client terms. - Group by page (from the URL relative to
websiteUrls), and within a page by content vs fix. - 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.
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.
- 12d ago First seen · 88 lines · 71 tokens per session scan A 8a8c854419d4
marker-client-report is a skill published in the GitHub repository marker-io/mcp-skills (7 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 1,269 once invoked, about $0.0004 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-31.
Other skills, from other repositories
meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
task-decomposition
Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.
constraint-driven-development
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or…
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.