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 stan-rym/liam-linkedin-ads-MCP --skill liam-weeklygit clone --depth 1 https://github.com/stan-rym/liam-linkedin-ads-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/stan-rym/liam-linkedin-ads-mcp/liam-weekly)<a href="https://agentmods.dev/skills/stan-rym/liam-linkedin-ads-mcp/liam-weekly"><img src="https://agentmods.dev/badge/skills/stan-rym/liam-linkedin-ads-mcp/liam-weekly/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/stan-rym/liam-linkedin-ads-mcp/liam-weekly"><img src="https://agentmods.dev/badge/skills/stan-rym/liam-linkedin-ads-mcp/liam-weekly.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.00080 | $0.00726 |
| Opus 5 | $0.00040 | $0.00363 |
| Sonnet 5 | $0.00016 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00073 |
Grade A, and why
liam-weekly 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 11d 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.
Liam: weekly snapshot
A snapshot, not a report. The same shape every week so weeks are comparable at a glance, short enough to read in a Slack message. Target under 40 lines of output.
How to reach Liam
Prefer the liam MCP tools if they are loaded. This skill wants two exact 7-day
windows, so use get_performance with explicit startDate/endDate (YYYY-MM-DD):
the last 7 full days, and the 7 before those. On the CLI, liam report summary -p last_7_days plus liam report trend <level> <id> -b weekly approximates it. Also pull
list_campaigns (structure and statuses), list_ads on active campaigns if ad-level
movers are wanted, and list_ad_changes for what was changed this week. Read-only.
What goes in
- Scoreboard: spend, impressions, CTR, conversions, cost per conversion for this week, each with the week-over-week delta.
- Movers: entities whose CTR, spend, or cost per conversion moved more than ~20% week over week, on at least ~1,000 impressions in both weeks. Cap at 3 up, 3 down.
- New this week: ads or campaigns that appeared (from
list_campaigns/list_ads), and journaled changes (list_ad_changes) so the reader connects moves to outcomes. - Flags: ACTIVE campaigns with zero delivery, audiences still matching or under 300 members, creatives with CTR down two-plus weeks running, conversion counts likely still lagging for the last 2 days.
- Do this week: at most 3 actions, imperative, each tied to a number above.
Rules
- Same section order every week; never add sections ad hoc.
- Deltas as signed percentages; money in account currency.
- No verdicts on entities below the volume floor; skip them silently here (the deep dives are liam-performance and liam-leads, and the snapshot should say so only when something big warrants it).
- If the week was quiet, say it in one line and keep the snapshot short rather than inflating noise into findings.
Report format
LinkedIn ads, <start> to <end>
Spend $X (+Y%) | Leads N (+Y%) | CPL $X (+Y%) | CTR X% (+Y%)
Up: ...
Down: ...
New: ...
Flags: ...
Do this week:
1. ...
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.
- 11d ago First seen · 66 lines · 80 tokens per session scan A 7d66c0f3461e
liam-weekly is a skill published in the GitHub repository stan-rym/liam-linkedin-ads-MCP (22 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 726 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…