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/Fmarzochi/EGCWrote 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/commands/fmarzochi/egc/auto-update)<a href="https://agentmods.dev/commands/fmarzochi/egc/auto-update"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/auto-update/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/commands/fmarzochi/egc/auto-update"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/auto-update.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.00014 | $0.00492 |
| Opus 5 | $0.00007 | $0.00246 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
auto-update 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 6d 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
Auto Update
Update EGC from its upstream repo and regenerate the current context's managed install using the original install-state request.
Usage
# Preview the update without mutating anything
ECC_ROOT="${GEMINI_PLUGIN_ROOT:-$(node -e "var r=(()=>{var e=process.env.GEMINI_PLUGIN_ROOT;if(e&&e.trim())return e.trim();var p=require('path'),f=require('fs'),h=require('os').homedir(),d=p.join(h,'.gemini'),q=p.join('scripts','lib','utils.js');if(f.existsSync(p.join(d,q)))return d;for(var s of [['egc'],['egc@egc'],['marketplace','egc'],['everything-gemini'],['everything-gemini@everything-gemini'],['marketplace','everything-gemini']]){var l=p.join(d,'plugins',...s);if(f.existsSync(p.join(l,q)))return l}try{for(var g of ['egc','everything-gemini']){var b=p.join(d,'plugins','cache',g);for(var o of f.readdirSync(b,{withFileTypes:true})){if(!o.isDirectory())continue;for(var v of f.readdirSync(p.join(b,o.name),{withFileTypes:true})){if(!v.isDirectory())continue;var c=p.join(b,o.name,v.name);if(f.existsSync(p.join(c,q)))return c}}}}catch(x){}return d})();console.log(r)")}"
node "$ECC_ROOT/scripts/auto-update.js" --dry-run
# Update only Cursor-managed files in the current project
node "$ECC_ROOT/scripts/auto-update.js" --target cursor
# Override the EGC repo root explicitly
node "$ECC_ROOT/scripts/auto-update.js" --repo-root /path/to/EGC
Notes
- This command uses the recorded install-state request and reruns
install-apply.jsafter pulling the latest repo changes. - Reinstall is intentional: it handles upstream renames and deletions that
repair.jscannot safely reconstruct from stale operations alone. - Use
--dry-runfirst if you want to see the reconstructed reinstall plan before mutating anything.
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.
- 6d ago First seen · 29 lines · 14 tokens per session scan A e87ff35f9469
auto-update is a command published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 492 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
revert
Git-aware undo by logical work unit (track, phase, or task).
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
summarize-changes
Summarize recent changes for standup, PR, or documentation.
handoff
Export a Waybill Bundle by default, or import one when requested.
ship-and-observe
Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.
commit-changes-main
Commit directly on main/master when explicitly allowed.