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/kok-o/contextos-agentsWrote 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/rules/kok-o/contextos-agents/gemini-precision)<a href="https://agentmods.dev/rules/kok-o/contextos-agents/gemini-precision"><img src="https://agentmods.dev/badge/rules/kok-o/contextos-agents/gemini-precision/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/rules/kok-o/contextos-agents/gemini-precision"><img src="https://agentmods.dev/badge/rules/kok-o/contextos-agents/gemini-precision.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.00030 | $0.00351 |
| Opus 5.5 | $0.00012 | $0.00140 |
| Sonnet 5.5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
gemini-precision 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 today.
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
Skill: gemini-precision
Resolve supporting resource paths relative to .agents/core/skills/gemini-precision. Read examples and references only when needed.
gemini-precision
Overview
Apply inspection and execution discipline when working with Gemini. Model-specific quality or performance gains require separate measured comparisons.
When to Use
Gemini implementation and debugging tasks, or an explicit request for this guidance.
Rules & Patterns
Inspect affected source, callers, symbols, runtime versions, and project checks. Implement the authorized behavior completely; never substitute stubs for a required integration. Preserve unrelated code. Choose checks by risk using engineering-workflow. Keep a persistent plan for substantial multi-file work when useful, not for every three tool calls. Explain meaningful decisions; role banners are optional.
Read EXAMPLES.md for a runnable validation example and its limits.
Code Examples
A validated calculation can be verified in isolation. It does not prove a payment was persisted or executed.
Validation Checklist
- The requested outcome and applicable failure cases are checked.
- Evidence names commands, results, scope, and limitations.
- Unrelated changes and existing authorization are preserved.
Common Mistakes
Guessing imports; declaring success without relevant evidence; repeated role banners; running every project gate for a typo; presenting model-specific gains without measurement.
Integration Notes
engineering-workflow owns the lifecycle, ponytail-mindset owns complexity choices, and security owns protected boundaries. This guidance supplements those skills for Gemini.
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.
- today First seen · 44 lines · 30 tokens per session scan A 927c7b27388f
gemini-precision is a cursor rule published in the GitHub repository kok-o/contextos-agents (10 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 351 once invoked, about $0.0001 per session on Opus 5.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-10-25.
Other cursor rules, from other repositories
vibeflow
Vibeflow spec-driven development methodology — guardrails, pipeline, and project knowledge system.
alembic-migrations
To add a non-nullable column and set a specific value for all existing rows without a persistent server default.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
shell-scripts
Shell Scripts.
mise
Mise.
cursorrules
═══════════════════════════════════════════════════════════ SPEC DRIVEN DEVELOPMENT — PROJECT CONSTITUTION Project: Freelance Time Tracker Version: v1.0.