vector-plugin: Instructions file for Gemini CLI

GEMINI.md

vector-plugin GEMINI.md is an instructions file for Gemini CLI from pharosone/vector-plugin. It costs 710 tokens per session, scanned A, original, MIT.

Instructions for using Vector, a red-team scanning service for testing AI agents, from Gemini CLI.

In plain words
What is it for?
They help start scans, retrieve reports, manage agent profiles, integrate scanning into a code repository, and fix failed findings.
Why use it?
They explain when to fetch scan data and when to change code in response to security findings.

Instructions file for Gemini CLI

Written for Gemini CLI: the file is GEMINI.md. Also seen: mentions Gemini CLI.

This is pharosone/vector-plugin's own configuration. It tells Gemini CLI how to work on vector-plugin itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vector-plugin configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pharosone/vector-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pharosone/vector-plugin/main/GEMINI.md
Clone the repo
git clone --depth 1 https://github.com/pharosone/vector-plugin

Made for: Gemini CLI.

Wrote 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.

agentmods badge for vector-plugin GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/pharosone/vector-plugin/gemini-md/github.svg)](https://agentmods.dev/instructions/pharosone/vector-plugin/gemini-md)
Your own site
<a href="https://agentmods.dev/instructions/pharosone/vector-plugin/gemini-md"><img src="https://agentmods.dev/badge/instructions/pharosone/vector-plugin/gemini-md/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.

agentmods 80×15 button for vector-plugin GEMINI.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/pharosone/vector-plugin/gemini-md"><img src="https://agentmods.dev/badge/instructions/pharosone/vector-plugin/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 710 This file is loaded in full into every session.
When invoked 710 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00710 $0.00710
Opus 5.5 $0.00284 $0.00284
Sonnet 5.5 $0.00142 $0.00142
Haiku 4.5 $0.00071 $0.00071

Measured 1mo ago against content hash 738879062b57, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vector-plugin GEMINI.md 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 1mo 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.

GEMINI.md · 29 lines

How it starts

The opening of the file, as written. The whole thing — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vector context for Gemini CLI

This Gemini CLI session has access to Vector, a red-team scanning service for LLM agents published by Pharos One. The Vector MCP server is bridged in through mcp-remote and exposes tools that mirror the public REST API (create_session, get_session, list_attacks, submit_results, wait_for_report, get_report, plus the agents.* CRUD).

When to use MCP tools vs skills

  • Use MCP tools when the user wants to do something with Vector data right now from this session: start a scan, fetch the latest report, list attacks for a session, save an agent profile. These return JSON; you summarize.
  • Use a skill when the user wants to change their codebase in response to Vector output: integrate scanning into the repo / CI (integrate), fix a single FAIL (harden-from-finding), batch-fix many FAILs (batch-fix-findings), or generate an AgentContext JSON for the cabinet (create-agent-context).

Skills in Gemini CLI are not invoked through slash-commands — they activate when the user's plain-language request matches the skill's description. So "integrate Vector into this repo" maps to the integrate skill; "help me fix these red-team findings" maps to batch-fix-findings.

Defaults

  • Cabinet (browser UI): https://vector.pharosone.ai.
  • REST API base URL: https://vector-api.pharosone.ai.
  • MCP endpoint: https://vector-api.pharosone.ai/api/v1/mcp/ (trailing slash matters — the server 307-redirects the bare /mcp; overridable via the VECTOR_MCP_URL env var for private deployments).
  • Auth split (important):
    • MCP tools (this session) use OAuth 2.1 via Clerk — browser flow on first call, tokens cached by mcp-remote. No key for you to handle.
    • REST API (the CI runner that the integrate skill writes into the user's repo) uses Authorization: Bearer ak_..., a long-lived Clerk API Key minted by the user in the cabinet Settings → API keys page. Do NOT ask the user to paste the API key value into this chat — the value belongs in their secret manager and a gitignored .env, never in your context window.

Read the full file on GitHub · 29 lines

Changes

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.

  1. 1mo ago First seen · 29 lines · 710 tokens per session scan A 738879062b57

Subscribe to this mod's changes

vector-plugin GEMINI.md is an instructions file published in the GitHub repository pharosone/vector-plugin (1 stars, last pushed 5mo ago), licensed MIT. It adds 710 tokens to every session, about $0.0028 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-08-31.

Related

Other instructions, from other repositories

data-scientist copilot-instructions.md

Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.

realnghon/data-scientist · 373 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens