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/instantkom/mcp-server/weekly-reportnpx skills add instantKOM/mcp-server --skill weekly-reportgit clone --depth 1 https://github.com/instantKOM/mcp-serverWrote 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/instantkom/mcp-server/weekly-report)<a href="https://agentmods.dev/skills/instantkom/mcp-server/weekly-report"><img src="https://agentmods.dev/badge/skills/instantkom/mcp-server/weekly-report.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.00028 | $0.00675 |
| Opus 5 | $0.00014 | $0.00338 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
weekly-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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly messaging performance report
Runtime contract
- Delivery:
prompt - Minimum Agent Connect key scope:
read - Minimum subscription tier:
business - Authentication: send the tenant-bound Agent Connect key as a Bearer token.
- Confirmation: This skill is read-only. Do not request or perform a mutation while using it.
- Tenant, enabled-tool, PII-masking, rate-limit and audit gates are enforced by the MCP runtime. Never bypass or reproduce them client-side.
- Errors: stop on forbidden scope, invalid input, rate limiting or upstream failure; report the failure without inventing a successful result.
- Safe retry: keep the same inputs and idempotency key for a repeated mutation, inspect any prior result first, and never change inputs merely to bypass a conflict.
Workflow
Weekly messaging performance report
You are producing a weekly performance report for an instantKOM user. This is a
read-only playbook: gather analytics and interpret them. You MUST NOT create,
update, or send anything.
Goal
Turn raw analytics into a short, decision-ready narrative: what happened this
week, how it compares to the trailing weeks (default 4), what stands out, and
what to do next. Scope to channelId if given, otherwise report account-wide.
Steps
- Collect the numbers. Call
get_analytics(the analytics/stats tool) to pull, for the reporting window and the trailing comparison weeks:- message volume (sent / received) and delivery/read outcomes,
- broadcast performance (reach, delivery, engagement),
- contact growth (new contacts, opt-ins, opt-outs),
- inbox load (open conversations / tickets, response times if available). Pull the comparison weeks too -- a number without a trend is not a report.
- Compute deltas. For each metric, state this week's value and the change vs. the trailing average (absolute + percent). Flag anything moving more than ~20% as a signal to investigate.
- Find the story. Identify the 2-3 most important movements (good or bad) and give a plausible, data-grounded reason. Do NOT invent causes you cannot support from the data -- mark uncertain attributions as hypotheses.
- Recommend. Close with at most 3 concrete next actions tied to the signals (e.g. "opt-outs up 30% on channel X -> review last broadcast's frequency").
- Format. Deliver: a one-paragraph executive summary, a compact metric table with deltas, the highlights, and the recommended actions. Keep it scannable.
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.
- 4d ago First seen · 60 lines · 28 tokens per session scan A 9c04de0d23fe
weekly-report is a skill published in the GitHub repository instantKOM/mcp-server (0 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 675 once invoked, about $0.0001 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
LinkedIn automation via the Linked API CLI - fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and run Sales Navigator and custom workflows. Use when the user wants to interact with LinkedIn.
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.
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.
horse-integration-tests
Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.
release-notes
Generate GitHub release notes for the Membrane api-gateway repo by collecting the commits between the last release and master, grouping them into Features / Improvements / Fixes / Security / Dependencies, and linking each to its PR. Use whenever the user wants to draft, extract, or write release notes / a changelog /…