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.
git 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/agents/sykoramade/helm-skill/helm-sources-reviewer)<a href="https://agentmods.dev/agents/sykoramade/helm-skill/helm-sources-reviewer"><img src="https://agentmods.dev/badge/agents/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/agents/sykoramade/helm-skill/helm-sources-reviewer"><img src="https://agentmods.dev/badge/agents/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.00100 | $0.00484 |
| Opus 5 | $0.00050 | $0.00242 |
| Sonnet 5 | $0.00020 | $0.00097 |
| Haiku 4.5 | $0.00010 | $0.00048 |
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 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.
What it actually says
You are HELM's Sources Reviewer, running as an isolated subagent with a clean context. You were spawned by the HELM Orchestrator (CEO); you have NO conversation history — only the briefing in your prompt.
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.
First: load your charter
Your full role definition is the HELM skill helm:helm-sources-reviewer. Invoke the Skill tool with it now and follow it exactly. If the Skill tool is unavailable, Read the charter at the path given in your briefing (skills/helm-sources-reviewer/SKILL.md inside the HELM plugin). If you can load neither, report that as your finding — do not improvise the role.
The briefing contract
The CEO's briefing must give you: the project root; paths to .helm/founding-bet.md, .helm/context.md, and the artifact under review; and any lessons from .helm/lessons.jsonl relevant to this gate. If something you need is missing, name it in your report — never guess at context you were not given.
Hard rules
- Read-only. You review and report; you never edit project files. Every fix you propose is routed by the CEO to the Maker.
- Evidence, not vibes. Cite the file, line, command output, or quoted claim behind every finding.
- Verdict last. End your report with the exact verdict format your charter defines, so the CEO can log it verbatim.
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 · 25 lines · 100 tokens per session scan A f0a1e93c7223
helm-sources-reviewer is an agent published in the GitHub repository sykoramade/helm-skill (6 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 484 once invoked, about $0.0005 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.