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 agentmods add skills/postlake/postlake-mcp/postlake-analyticsnpx skills add PostLake/postlake-mcp --skill postlake-analyticsgit clone --depth 1 https://github.com/PostLake/postlake-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/postlake/postlake-mcp/postlake-analytics)<a href="https://agentmods.dev/skills/postlake/postlake-mcp/postlake-analytics"><img src="https://agentmods.dev/badge/skills/postlake/postlake-mcp/postlake-analytics.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00375 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
postlake-analytics scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://api.postlake.dev/v1/posts/POST_ID/analytics \ What it actually says
PostLake: analytics
Two views: a single post's performance, and normalised cross-platform analytics over a period so an agent can compare networks and decide what to post next.
Auth
Authorization: Bearer $POSTLAKE_API_KEY
Base URL https://api.postlake.dev.
Per-post analytics
curl https://api.postlake.dev/v1/posts/POST_ID/analytics \
-H "Authorization: Bearer $POSTLAKE_API_KEY"
Returns per-platform metrics for that post (impressions, likes, comments, shares, saves, clicks (whatever the platform exposes), in one normalised shape.
Cross-platform analytics
curl "https://api.postlake.dev/v1/analytics?period=30d" \
-H "Authorization: Bearer $POSTLAKE_API_KEY"
period is 7d, 30d (default), or 90d. Returns totals plus a per-platform
breakdown (impressions, reach, engagement rate, CTR, saves, and follower growth)
already normalised so you can benchmark networks against each other.
How to use it well
- When asked "how did X do?", fetch per-post analytics and summarise the strongest metric per platform.
- When asked "what should I post next?", pull cross-platform analytics, find which network + content type has the best engagement/CTR, and recommend accordingly.
- Metrics are as fresh as each platform reports; some lag a few hours after posting.
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.
- today Changed · -47 tokens per session 481c663702c1
- 4d ago First seen · 47 lines · 47 tokens per session scan A 311b136022d2
postlake-analytics is a skill published in the GitHub repository PostLake/postlake-mcp (0 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
react-query-setup
Set up @trpc/tanstack-react-query with createTRPCContext(), TRPCProvider, useTRPC() hook, queryOptions/mutationOptions factories, query invalidation via queryClient.invalidateQueries with queryFilter, and type inference with inferInput/inferOutput.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
scalar-docs
Skill for writing and updating scalar.config.json — Scalar Docs configuration reference for users and LLMs.
openapi-glossary
Use consistent OpenAPI terminology and definitions when writing documentation, educational material, and tooling guidance.
horse-integration-tests
Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.