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/elvisun/newsjack/coverage-tracker-setupnpx skills add elvisun/newsjack --skill coverage-tracker-setupgit clone --depth 1 https://github.com/elvisun/newsjackWrote 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/elvisun/newsjack/coverage-tracker-setup)<a href="https://agentmods.dev/skills/elvisun/newsjack/coverage-tracker-setup"><img src="https://agentmods.dev/badge/skills/elvisun/newsjack/coverage-tracker-setup.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.00043 | $0.01303 |
| Opus 5 | $0.00022 | $0.00651 |
| Sonnet 5 | $0.00009 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
coverage-tracker-setup 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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Tracker Setup
This sets up a simple keyword tracker that the coverage-tracker skill runs for you. Think of it like a Google Alert: it watches for new coverage of the keywords you care about and tells you when something real shows up.
It is deliberately a different job from setting up newsjack monitoring. A coverage tracker answers "did my keyword get real coverage?" Newsjack monitoring (newsjack-monitor-setup) answers a bigger question: "can my company jump into a broader news story?" If the user wants the second one, use that skill instead.
Where you're running this
Two situations, and they change what you can finish here:
- You can save files and run commands (Claude Code, Codex, OpenClaw, Hermes, or a similar setup with shell, file, and network access). Here you can do the whole thing: save the tracker, run it once, and hand the recurring schedule to your agent. Before you decide you can't run the CLI, check whether
newsjackis installed. It ships as a prebuilt, bundled binary — you do not need Go, a compiler, or any build/install step. Never look for a Go toolchain or tell the user they need a "Go environment" without checking first: runnewsjack --version; if that's not onPATH, try the bundled location~/.newsjack/bin/newsjack --versionand use that full path everywhere if it works. The bundled binary is almost always already installed — verify, don't assume it's missing. - You're in a plain chat window (Claude.ai, ChatGPT, Claude Cowork, or anything without file/command access). Here you can only draft. Write out the tracker config and the schedule prompt, then tell the user to move to a setup that can save and run things. Don't try to install or run anything, and don't tell the user it was saved or scheduled when it wasn't.
What to ask the user
Only ask for what you don't already know:
- a name for the tracker
- the keywords to watch (as many as they want)
- for each keyword, one short note on what it actually means: which company, product, or person should it point to? This is what later filters out wrong matches.
- optionally, words or uses to ignore when a keyword is ambiguous (for example, a common word that also happens to be a brand name)
- how often to check: every morning, twice a day, or hourly
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.
- 5d ago First seen · 96 lines · 43 tokens per session scan A 6e31a5317c96
coverage-tracker-setup is a skill published in the GitHub repository elvisun/newsjack (664 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,303 once invoked, about $0.0002 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
conversion-audit
Use this skill to run a scored 53-point conversion audit covering customer focus, narrative, copy, design, calls to action, and proof. Trigger it when a landing, sales, product, or ad destination page needs diagnosis, pre-launch review, or prioritized conversion fixes.
channel-discovery
Use this skill to identify and score acquisition channels by audience fit, speed, cost, effort, and learning value, then recommend the top three. Trigger it when choosing where to reach a defined audience, planning go-to-market, or replacing an underperforming channel.
ad-angles
Use this skill to brainstorm ad concepts across problem, solution, comparison, proof, and curiosity angles, formats, and visual styles. Trigger it when planning a campaign, refreshing stale creative, testing messaging, or preparing creative briefs.
ad-campaign-analyzer
Use this skill to grade running ads as Red (stop), Yellow (hold), or Green (scale), detect creative fatigue, analyze LTV:CAC, and recommend scaling actions. Trigger it when reviewing campaign exports or deciding what to kill, keep, or scale.
ad-creative
Use this skill to turn ad concepts into HTML creative in cookie-cutter, ugly, meme, branded, or native styles, with optional Playwright screenshots. Trigger it when producing, varying, or iterating visual ad assets for testing.
content-repurposer
Use this skill to turn a blog post, newsletter, podcast, video transcript, or other long-form source into a week of short-form social content using the Hub & Spoke method. Trigger it when repurposing an existing source rather than writing from a topic alone.