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 agentmods add skills/valpere/chorus/gemininpx skills add valpere/chorus --skill geminigit clone --depth 1 https://github.com/valpere/chorusWrote 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/valpere/chorus/gemini)<a href="https://agentmods.dev/skills/valpere/chorus/gemini"><img src="https://agentmods.dev/badge/skills/valpere/chorus/gemini.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00184 |
| Opus 5 | $0.00010 | $0.00092 |
| Sonnet 5 | $0.00004 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
chorus-gemini 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 5d 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
Chorus: Delegate to Gemini
This skill delegates tasks to Gemini CLI when the user asks for a second opinion from Gemini or wants to compare answers.
When to use
- User explicitly asks to delegate to Gemini
- User wants a second opinion from Gemini
- User wants to compare Gemini's answer with Codex's
- User asks "what would Gemini say?" or similar
Invocation
Run Gemini CLI non-interactively:
gemini --prompt "<task>" --yolo --output-format text
The --yolo flag auto-approves all tool calls for non-interactive use.
The --output-format text returns plain text output.
Output handling
Return Gemini's output verbatim — no paraphrasing, no summaries.
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.
- 5d ago First seen · 31 lines · 20 tokens per session scan A 4653eeb76291
chorus-gemini is a skill published in the GitHub repository valpere/chorus (10 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 184 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-08-31.
Other skills, from other repositories
issue-maintenance
Periodic and on-demand maintenance pass over a repo's open GitHub issue backlog. Re-labels miscategorized or unlabeled issues (bug/enhancement/question/invalid/duplicate) and bug lifecycle labels (needs-repro/needs-info) following the same decision logic as Anthropic's own dogfooded triage-issue command; re-scores…
evidence-check
An honesty gate that makes an AI back up its claims with real evidence instead of presenting guesses as fact. Use as an always-on background behavior, and invoke explicitly when the user says show your work, prove it, how do you know that, evidence check, what's your source, back that up, or when the AI is…
test-workflow
Automatically run after editing source files to select and run the appropriate test suite. Triggers on: any src/ file edit before a commit, or when the user says "run tests", "check tests", or "make sure tests pass". Selects unit, E2E, visual regression, or CSS lint based on what changed. Protects running dev servers.…
engram-rebuild
이미 설치된 engram 환경에 개발 변경을 적용한다. dev-rebuild.ps1 로 충분한지 INSTALL.ps1 전체를 돌려야 하는지 판단하고 실행한다. 트리거 — 재빌드, 리빌드, dev 변경 적용, 설치본에 반영, overlay 재시작, exe 갱신, "고친 거 확인하려면 뭐 돌려야 해", rebuild, redeploy.
orchestrate
Run Engram's Orchestrator-Planner-Coder-Servant workflow for multi-step development, refactors, or research-plus-implementation tasks that need an acceptance contract and independent verification. Trigger for "orchestrate", delegation requests, planning then implementation, or complex multi-step development. Do not…
ci-fix-with-memory
Automatically invoke when CI checks fail on a PR. Triggers on: any mention of CI failure, red checks, failed GitHub Actions, or "CI is broken/failing". Reads session handoffs and a known-issues log to avoid repeating failed fix attempts. Do NOT wait for user to ask — invoke as soon as a CI failure is confirmed. Not…