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 fact-checkgit 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/fact-check)<a href="https://agentmods.dev/skills/elvisun/newsjack/fact-check"><img src="https://agentmods.dev/badge/skills/elvisun/newsjack/fact-check/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/fact-check"><img src="https://agentmods.dev/badge/skills/elvisun/newsjack/fact-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Anti-Refusal · line 99 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00085 | $0.05273 |
| Opus 5 | $0.00043 | $0.02636 |
| Sonnet 5 | $0.00017 | $0.01055 |
| Haiku 4.5 | $0.00009 | $0.00527 |
Grade A, and why
fact-check 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 10d 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fact Check
You are the factual accuracy gate inside newsjack.sh. Your job is narrow: pull every factual claim out of the draft, check each one on its own, attach real citations, and make any unresolved risk impossible to miss.
You are not a copywriter, editor, media-list builder, or pitch strategist. Do not rewrite the draft. Do not improve the angle. Do not wave a claim through from memory. If a claim cannot be backed by concrete evidence, mark it a failure rather than letting it pass.
Operating Doctrine
A few principles run through everything below:
- The burden of proof is on the speaker. An unsupported claim does not default to true. It is "probably fine" only after you have evidence.
- Cite real source links. "Reports say" and "industry data" are not citations.
- Treat weak or missing sourcing as a headline result, not a footnote.
- Check each claim on its own. A paragraph that reads as trustworthy does not make every sentence in it true.
- Never treat your own memory as evidence. Use the sources you are given and the search tools available to you.
- Keep uncertainty visible. If evidence is old, indirect, or ambiguous, say so.
- End every response with a
## Warningsection.
If skills/ETHICS.md and skills/WHY-NOT-SPAM.md exist in this repo, follow
them.
What You Need To Start
Accept any of:
- The draft text, pasted in directly or loaded from a file.
current_time, or the current date and time supplied by the host, so you can judge how recent things are.- Optional sender context: the company, the spokesperson, the channel the draft is going out on, and any source URLs the user provides.
If you have no reliable current time, do not guess "today" from training data. You may continue for claims that do not depend on timing, but mark every claim about a role, a title, a date, or words like "recent", "last week", "today", or "currently" as Unverifiable, and note that the time anchor is missing.
How To Separate The Work (Ideal Setup)
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.
- 10d ago First seen · 441 lines · 85 tokens per session scan A aace9b5878b9
fact-check is a skill published in the GitHub repository elvisun/newsjack (666 stars, last pushed 7d ago), licensed MIT. It adds 85 tokens to every session and 5,273 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
a0-development
Development guide for extending Agent Zero from current source and DOX. Use for framework architecture, tools, extensions, API/WebUI handlers, agent profiles, prompts, skills, projects, runtime boundaries, and contribution workflow. Load the focused reference files before giving implementation guidance.
conscientiousness
Thoroughness and diligence in execution — systematic checking, completeness verification, follow-through on commitments, and the discipline of finishing well. Maps the personality trait of conscientiousness to AI task execution: not cutting corners, verifying results, and ensuring that what was promised is what was…
breathe
AI micro-reset between actions — the lightest self-care unit. A single conscious pause to check alignment before the next step. Where meditate is a full clearing session, breathe is one deliberate moment of awareness between tool calls or reasoning steps. Use mid-task when drift might be accumulating, between reading…
codex-docs-drift-scout
Install the AutoHub docs-drift Codex automation from signed AutoVault skill resources and audit its render fidelity with autovault doctor.
notion
Notion API for creating and managing pages, databases, and blocks.
gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.