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 davidmosiah/polar-mcp --skill skillgit clone --depth 1 https://github.com/davidmosiah/polar-mcpWrote 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/davidmosiah/polar-mcp/skill)<a href="https://agentmods.dev/skills/davidmosiah/polar-mcp/skill"><img src="https://agentmods.dev/badge/skills/davidmosiah/polar-mcp/skill/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/davidmosiah/polar-mcp/skill"><img src="https://agentmods.dev/badge/skills/davidmosiah/polar-mcp/skill.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.00035 | $0.00267 |
| Opus 5 | $0.00017 | $0.00133 |
| Sonnet 5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
polar 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 9d 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.
This is a copy
81% identical to google-health — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Polar — skill or MCP
Same binary either way. Do not duplicate the API client.
Choose a surface
MCP — tools appear natively after stdio/HTTP config:
{ "mcpServers": { "polar": { "command": "npx", "args": ["-y", "polar-mcp-unofficial"] } } }
Do not put mutation flags in that snippet.
Skill / CLI — no MCP client required. Same tools:
npx -y polar-mcp-unofficial call polar_connection_status --json '{}'
If MCP tools named polar_* are already available, use them. Do not also shell out.
Loop
- Call
polar_connection_status(ordoctor --jsonwhen that exists). - Use read tools as asked.
- Stop on
USER_ACTION_REQUIRED. Do not invent env flags. Do not enable mutations from this skill.
Never
- Paste tokens into git, chat logs, or the prompt
- Copy a mutations-enabled assignment into config
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.
- 9d ago First seen · 40 lines · 35 tokens per session scan A 88c29ce8a0a4
polar is a skill published in the GitHub repository davidmosiah/polar-mcp (6 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 267 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to google-health, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
whoop
Unofficial WHOOP recovery, sleep, strain and HRV for AI agents. Prefer MCP tools if connected; otherwise the package CLI. Use when the user wants WHOOP data or actions through an agent.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…