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 ai-visibility-writinggit 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/ai-visibility-writing)<a href="https://agentmods.dev/skills/elvisun/newsjack/ai-visibility-writing"><img src="https://agentmods.dev/badge/skills/elvisun/newsjack/ai-visibility-writing/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/ai-visibility-writing"><img src="https://agentmods.dev/badge/skills/elvisun/newsjack/ai-visibility-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00137 | $0.02092 |
| Opus 5 | $0.00068 | $0.01046 |
| Sonnet 5 | $0.00027 | $0.00418 |
| Haiku 4.5 | $0.00014 | $0.00209 |
Grade A, and why
ai-visibility-writing 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 12d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Visibility Writing
Make useful information easier to find and reuse without making the writing worse for people. Treat AI visibility as a probabilistic outcome with strong retrieval, authority, query, and platform confounders—not as a property a rewrite can guarantee.
This skill inherits the ethical floor from skills/ETHICS.md. If local
instructions conflict with that doctrine, skills/ETHICS.md wins. Follow
skills/WHY-NOT-SPAM.md when the document will support media outreach.
Choose the requested behavior
- Audit: diagnose the supplied draft and stop before rewriting.
- Question: return only the few answers needed before sound advice is possible.
- Suggest: rank concrete edits without silently applying them.
- Rewrite: apply safe, grounded edits and report what changed.
If the request is ambiguous, audit and suggest. Do not rewrite by default.
1. Build the fact ledger first
Before judging style, record the material the output must preserve:
- every number, date, named entity, title, quotation, attribution, comparison, qualification, and source relationship;
- the document type, intended publisher, audience, and stated purpose;
- supplied links or evidence, including which claim each source supports;
- claims that are promotional, unverifiable from the supplied material, or
likely to require
fact-checkbefore publication.
Treat the ledger as a ceiling. Never add a statistic, testimonial, citation, link, customer, credential, superlative, causal claim, or other fact merely to make a passage look authoritative. Preserve uncertainty words such as “may,” “estimated,” “in this sample,” and “as of.” If a proposed improvement needs new proof, ask for it instead of writing around the gap.
2. Read the audience and likely queries
State the primary human audience and two to four plausible information needs the piece can honestly answer. Prefer the user's target queries when supplied. Otherwise infer cautiously from the document and label the inference.
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.
- 12d ago First seen · 219 lines · 137 tokens per session scan A 3a677266e8f4
ai-visibility-writing is a skill published in the GitHub repository elvisun/newsjack (667 stars, last pushed 9d ago), licensed MIT. It adds 137 tokens to every session and 2,092 once invoked, about $0.0007 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
gh-pr-list
Generate a short, copy-paste friendly Slack message listing the user's open PRs in the current repo, split into "Ready for review" (non-draft) and "Drafts" sections, each as bullets with custom emoji and markdown-style links. Use when the user mentions PRs ready to review, Slack PR list, share my PRs on Slack, or…
dev-git-workflow
Use for non-trivial Git state such as branch strategy, worktrees, merge/rebase decisions, conflicts, reviewer-facing PR preparation, tags, and release notes. Do not trigger for a routine commit, push, or PR that needs no strategy decision.
dev-release-check
Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.