Borrowing it
Nothing to install: this file belongs to agarwalvishal/claude-chat-exporter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agarwalvishal/claude-chat-exporter/main/.claude/skills/add-sponsor/SKILL.mdgit clone --depth 1 https://github.com/agarwalvishal/claude-chat-exporterWrote 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/agarwalvishal/claude-chat-exporter/add-sponsor)<a href="https://agentmods.dev/skills/agarwalvishal/claude-chat-exporter/add-sponsor"><img src="https://agentmods.dev/badge/skills/agarwalvishal/claude-chat-exporter/add-sponsor/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/agarwalvishal/claude-chat-exporter/add-sponsor"><img src="https://agentmods.dev/badge/skills/agarwalvishal/claude-chat-exporter/add-sponsor.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.00050 | $0.01140 |
| Opus 5 | $0.00025 | $0.00570 |
| Sonnet 5 | $0.00010 | $0.00228 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
add-sponsor 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 13d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a sponsor
Assets live in docs/sponsors/<name>.svg. Three edits, all by hand — there is no CI.
README — one block under the install badge, holding both tiers
Company first, Team after, the same height="28" for every logo, and no taglines (they
force a vertical layout and push the project's own pitch off the screen). The label links to
the Support section so the policy is one click away:
<p align="center">
<sub><b><a href="#support-this-project">Supported by</a></b></sub><br>
<a href="https://acme.example" rel="sponsored noopener"><img src="docs/sponsors/acme.svg" alt="Acme" height="28"></a>
<a href="https://globex.example" rel="sponsored noopener"><img src="docs/sponsors/globex.svg" alt="Globex" height="28"></a>
</p>
Do not add a "still MIT / still private" line beside the logos. Both claims are already in the README's first sentence, above the badge.
Install page — Company tier only
A row in the footer of docs/index.html. The footer is also where the update notice sends
returning users (d.onclick = window.open(P) in the shim), which is what the tier sells.
<span class="sponsors"><span class="lbl">Supported by</span>
<a href="https://acme.example" target="_blank" rel="sponsored noopener"><img src="sponsors/acme.svg" alt="Acme" height="28"></a>
</span>
footer .sponsors { display: flex; align-items: center; gap: .5rem .9rem; flex-wrap: wrap; }
footer .sponsors .lbl { font-size: .8rem; color: var(--muted); }
footer .sponsors img { height: 28px; width: auto; max-width: 110px; opacity: .85; }
footer .sponsors a:hover img { opacity: 1; }
Accepting the asset — sanitise before committing
Committing the logo is the right call: it keeps the install page's promise that it makes no third-party requests. Hot-linking a sponsor's own domain would let them log every visitor's IP. (refined-github does the same; larger projects instead serve from their funding platform. Nobody loads a sponsor's server.)
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.
- 13d ago First seen · 91 lines · 50 tokens per session scan A 8e1b0a2eb0d1
add-sponsor is a skill published in the GitHub repository agarwalvishal/claude-chat-exporter (678 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 1,140 once invoked, about $0.0003 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
github-flow-for-claude-on-web
Complete GitHub workflow for Claude Code on the web. ALL GitHub operations MUST use REST API (never gh CLI). Includes branch naming (claude/-sessionId), push retry logic, PR/issue management via API, and complete workflows. Use for all GitHub interactions in Claude Code web environment.
vibing-orchestrate
A coordinator for splitting independent tasks among separate vibing.nvim chats, a Neovim interface for working with coding agents, and combining their results.
self-testing
E2E self-testing workflow for vibing.nvim using a separate Neovim instance controlled over RPC. Use when writing or debugging E2E tests, running npm run test:e2e, or executing the 3-try auto-fix rule after implementing a feature. Covers the…
test-design
Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking…
vibing-chat-recall
Use when a vibing.nvim chat session's context feels lost or discontinuous — after a session reset, a dropped connection, or when Claude's own reasoning no longer matches what was discussed earlier in this conversation. Re-reads this conversation's own chat buffer (the buffer announced via the "Current vibing.nvim chat…
vibing-chat-search
A search tool for finding earlier vibing.nvim conversations by topic. It searches chat files for words and phrases, then checks the matching conversations for relevance.