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-insightsgit 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-insights)<a href="https://agentmods.dev/skills/marker-io/mcp-skills/marker-insights"><img src="https://agentmods.dev/badge/skills/marker-io/mcp-skills/marker-insights/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-insights"><img src="https://agentmods.dev/badge/skills/marker-io/mcp-skills/marker-insights.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.00077 | $0.01022 |
| Opus 5.5 | $0.00031 | $0.00409 |
| Sonnet 5.5 | $0.00015 | $0.00204 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
marker-insights 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.
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-insights
Aggregate Marker.io website feedback into recurring patterns and a prioritized brief: what keeps coming back, which pages attract the most reports, and how much is content versus functional. Built for digital agencies and in-house website teams, where most feedback is content (typos, copy, images, links) and the rest is functional bugs.
When to use
"What are the most common issues on the site", "which pages get the most feedback", "are there recurring
content problems", "what's our content-vs-bug split", "feedback health of <site>". This is pattern
analysis across many reports, not per-issue triage (marker-triage) or fixing one report
(marker-bug-to-fix).
Steps
- Resolve the project(s) and read
project_getfor the site'swebsiteUrls(used to turn each issue URL into a page). For a multi-site view, repeat and pool the results. - Pull a wide window with
issues_list(paginatelimit/offsetfully; usually weeks to months). Keep fields lean:markerId,title,status,url,createdAt. Drill intoissue_get/issue_get_context/issue_get_screenshotonly on a sample per cluster. - Classify every report as content (typo, copy/wording, wrong number or fact, image/media, broken link, layout/spacing, translation) or functional (form, navigation, JavaScript error, responsive break, performance). Marker does not expose an issue's type to read, so infer it from the title, page URL, and — when unclear — the screenshot.
- Cluster within each class by page (from the URL) and by theme. Count frequency and note severity, weighing how prominent the page is (a homepage typo is low-severity but high-visibility).
- Identify: the highest-feedback pages, recurring content problems (the same fix showing up again and
again), the content-vs-functional ratio, the trend over time (bucket by
createdAt), and any single root cause behind many reports (e.g. one stale data source feeding several pages).
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 · 77 tokens per session scan A 6f674c45f109
marker-insights is a skill published in the GitHub repository marker-io/mcp-skills (7 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 1,022 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.
marker-insights compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| marker-insightsmarker-io/mcp-skills | Skill | 7 | 5mo ago | MIT | A | 77 | 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 |