Newsjack.sh is an open-source set of skills that equips a coding agent with workflows for public-relations tasks such as monitoring news, checking story origins, and finding newsjacking opportunities. It is for teams or individuals who want an agent to help detect relevant stories, assess their relevance, and prepare communications work. The catalogue entries are Newsjack.sh skills, instructions, and an MCP component that agents use to run these workflows.
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 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/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/elvisun/newsjack/coverage-tracker-setup"><img src="https://agentmods.dev/badge/skills/elvisun/newsjack/coverage-tracker-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 17 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00043 | $0.01310 |
| Opus 5.5 | $0.00017 | $0.00524 |
| Sonnet 5.5 | $0.00009 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
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 16d 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 — 98 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.
- 16d ago Changed · +2 lines 2ccc76107633
- 1mo 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 (1,573 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,310 once invoked, about $0.0002 per session on Opus 5.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
sdlc-lld-workflow
Use to create or refine LLD for modules, interfaces, state machines, data structures, errors, transactions, and tests.
dev-release-check
Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.
dev-test-strategy
Use to design or validate test plans, unit/integration/e2e coverage, automation, CI checks, fixtures, and regression scope.
user-story-writer
Escribir historias de usuario bien estructuradas con criterios de aceptación y casos extremos. Úsalo cuando te pidan escribir historias de usuario, crear tickets a partir de un resumen de características, convertir un PRD en historias o redactar criterios de aceptación. Produce historias listas para estimar en formato…
prompt-regression-suite
Design a regression test suite that catches an LLM feature getting worse when the prompt, model, or context changes. Use when asked to stop prompt changes breaking production, set up golden tests or CI gates for an LLM feature, or test a model/prompt upgrade before shipping it. Produces a golden case set, per-case…
ai-agent-reliability
Make an AI agent or automation reliable enough to trust — the tests, checks, and guardrails that catch its failures before they reach anything real. Use when asked how do I test my AI agent, make my automation reliable, my agent works sometimes, or how do I trust an AI workflow in production. Produces a map of where…