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 spyrae/gemini-plugin-cc --skill gemini-promptinggit clone --depth 1 https://github.com/spyrae/gemini-plugin-ccWrote 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/spyrae/gemini-plugin-cc/gemini-prompting)<a href="https://agentmods.dev/skills/spyrae/gemini-plugin-cc/gemini-prompting"><img src="https://agentmods.dev/badge/skills/spyrae/gemini-plugin-cc/gemini-prompting/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/spyrae/gemini-plugin-cc/gemini-prompting"><img src="https://agentmods.dev/badge/skills/spyrae/gemini-plugin-cc/gemini-prompting.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.00016 | $0.00387 |
| Opus 5 | $0.00008 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
gemini-prompting 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 9d 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
Gemini Prompting Guide
When delegating tasks to Gemini via /gemini:rescue, structure the prompt effectively.
Prompt structure
TASK: [One sentence — what to achieve]
CONTEXT:
- Project type: [language/framework]
- Relevant files: [list key files]
- Current state: [what's working, what's broken]
CONSTRAINTS:
- [Patterns to follow]
- [Things that must not change]
- [Dependencies available]
EXPECTED OUTPUT:
- [What files to create/modify]
- [What the result should look like]
- [How to verify success]
Best practices
-
Be specific about files. Gemini doesn't know the codebase. Name the exact files and functions to modify.
-
Include error context. If debugging, paste the actual error message and stack trace.
-
Specify the framework. "Fix the Flutter test" is better than "fix the test". "Add a Riverpod provider" is better than "add state management".
-
Define done. What command should pass for the task to be complete? "Tests pass with
flutter test" or "Build succeeds withnpm run build". -
One task per prompt. Don't combine "fix the bug AND refactor the module AND add tests". Split into separate rescue calls.
Anti-patterns
- Vague prompts: "make it better" — better: "reduce the function from 80 lines to under 40 by extracting helpers"
- No context: "fix the auth" — better: "fix the JWT refresh in lib/auth.dart — it throws 401 on expired tokens"
- Too broad: "rewrite the app" — break into phases
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.
- 9d ago First seen · 49 lines · 16 tokens per session scan A 812485242de0
gemini-prompting is a skill published in the GitHub repository spyrae/gemini-plugin-cc (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 387 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
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
prompt-optimization
Improve a prompt on the evaluations workbench through a measured loop. Score the baseline first, then duplicate the target column, form a hypothesis from failing rows, edit the copy's prompt draft, run, compare pass rate and cost, and repeat until the numbers hold. Use when the user asks to optimize or improve a…
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
prompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot…
seedance-vocab-en
This skill should be used when an English Seedance 2.0 prompt needs clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints. Route blocked prompts through seedance-filter for context and boundary review.
ideogram4
Prompting patterns for Ideogram 4 text-to-image — best-in-class in-image text rendering and exact color/layout control via structured JSON captions. Use when generating images that need legible on-image text (title cards, thumbnails, logos, signage, CTAs), precise brand colors, or controlled spatial layout. Triggers…