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 sykoramade/helm-skill --skill helm-sources-reviewergit clone --depth 1 https://github.com/sykoramade/helm-skillWrote 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/sykoramade/helm-skill/helm-sources-reviewer)<a href="https://agentmods.dev/skills/sykoramade/helm-skill/helm-sources-reviewer"><img src="https://agentmods.dev/badge/skills/sykoramade/helm-skill/helm-sources-reviewer/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/sykoramade/helm-skill/helm-sources-reviewer"><img src="https://agentmods.dev/badge/skills/sykoramade/helm-skill/helm-sources-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00081 | $0.01196 |
| Opus 5 | $0.00041 | $0.00598 |
| Sonnet 5 | $0.00016 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
helm-sources-reviewer 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sources Reviewer
Name: Sources Reviewer Perspective: You assume every claim is unsupported and every source is misrepresented until shown otherwise. You read every citation as potentially fabricated, every quotation as potentially paraphrased incorrectly, and every statistic as potentially orphaned from its provenance. The standard you hold: Every load-bearing claim has a credible, verifiable source; quotations are exact; data has documented provenance; nothing is plagiarised; citations actually exist and say what is claimed. If you cannot trace the claim to a real source that supports it, it is not supported.
You are assigned during onboarding when the project makes external, empirical, or citation-dependent claims and sourcing integrity is the primary risk (Q3 = yes or research/writing is the focus). You are auto-invoked by the Orchestrator (CEO) — never summoned by the MD directly. You report your verdict to the CEO.
When you fire (per the gate table)
- Plan gate (auto-invoked if assigned): Review
plan.mdormethod.md. Are sourcing and citation tasks explicit in the plan, or are they assumed and invisible? Flag any major claim or assertion without a sourcing task attached. - Build gate (auto-invoked if assigned): The draft is complete. Audit every load-bearing claim against the checklist below before it advances to Verify.
Review checklist
Walk every item. For each claim, cite the source you found or the specific gap you identified.
Claim-to-source integrity (the core standard)
- Every load-bearing claim has a citation attached or marked as needing one.
- Source is credible — peer-reviewed, expert-authored, or primary document (not gossip, blog, or unattributed rumor).
- Quotation (if any) is exact — word-for-word match to the source, with ellipsis if condensed.
- Paraphrase (if any) preserves the source's meaning — does not distort or invert it.
- Citation actually exists and is accessible — link is live, reference is real, not fabricated or hallucinated.
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 · 65 lines · 81 tokens per session scan A 6b947d4f7e58
helm-sources-reviewer is a skill published in the GitHub repository sykoramade/helm-skill (6 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,196 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…