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/edithatogo/sourcerightWrote 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/plugins/edithatogo/sourceright/gemini-sourceright)<a href="https://agentmods.dev/plugins/edithatogo/sourceright/gemini-sourceright"><img src="https://agentmods.dev/badge/plugins/edithatogo/sourceright/gemini-sourceright/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/plugins/edithatogo/sourceright/gemini-sourceright"><img src="https://agentmods.dev/badge/plugins/edithatogo/sourceright/gemini-sourceright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sourceright 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 4d 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
{
"name": "sourceright",
"version": "0.1.20",
"description": "Reference verification MCP for Gemini CLI — CSL integrity, review queues, and audited write plans via sourceright mcp.",
"mcpServers": {
"sourceright": {
"command": "sourceright",
"args": ["mcp"]
}
},
"contextFileName": "GEMINI.md"
}
What ships with it
2 files beside gemini-extension.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 13 lines scan A 35070b321a3d
sourceright is a plugin published in the GitHub repository edithatogo/sourceright (1 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-08.
Other plugins, from other repositories
citevahti
CiteVahti — citation integrity for manuscripts. Human-first blinded claim checking with PubMed, decision-gated Zotero write-back, and a hash-chained audit trail; plus an AI-assisted drafting skill that writes only from checked claims.
endnote-for-word
Find DOI-verified research papers, import RIS, and create native IEEE EndNote CWYW citations and bibliographies in Microsoft Word.
agent-deck
Complete guide for managing AI coding agent sessions via agent-deck CLI - session lifecycle, MCP management, groups, profiles, and automation.
jk
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
b2c-cli
B2C CLI Skills for Salesforce Commerce Cloud development.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.