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 ThirdKeyAI/symbi-gemini-cli --skill symbi-verifygit clone --depth 1 https://github.com/ThirdKeyAI/symbi-gemini-cliWrote 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/thirdkeyai/symbi-gemini-cli/symbi-verify)<a href="https://agentmods.dev/skills/thirdkeyai/symbi-gemini-cli/symbi-verify"><img src="https://agentmods.dev/badge/skills/thirdkeyai/symbi-gemini-cli/symbi-verify.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.1 | $0.00033 | $0.00259 |
| Opus 5 | $0.00016 | $0.00130 |
| Sonnet 5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
symbi-verify 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- symbi-verify — 100% identical, 0 lines differ
What it actually says
SchemaPin Verification
Verify the cryptographic integrity of MCP tool schemas to ensure they haven't been tampered with.
Verification Process
- Identify the MCP server to verify (from the extension manifest or the user's request)
- Use the
symbi__verify_schematool to check the schema - Report the verification result:
- Verified: Schema signature matches the publisher's key
- TOFU: First-time use, key has been pinned for future verification
- Failed: Schema has been modified since signing -- DO NOT USE
- No signature: Schema is unsigned -- warn the user about risks
When to Verify
- Before first use of any new MCP tool
- After updating MCP server configurations
- When security audit is requested
- When a tool returns unexpected results
Note on Tool Names
In Gemini CLI, MCP tools are prefixed with the server alias and double underscore.
The symbi MCP tools are accessed as symbi__verify_schema, symbi__list_agents, etc.
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.
- 7d ago First seen · 31 lines · 33 tokens per session scan A 2bfecac3c32f
symbi-verify is a skill published in the GitHub repository ThirdKeyAI/symbi-gemini-cli (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 259 once invoked, about $0.0002 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
symbi-agent-sdk
Generate boilerplate for wrapping Gemini CLI agents in ORGA governance. Use when building headless agents that run inside Symbiont's CliExecutor or when integrating Gemini CLI with Symbiont's trust stack.
symbi-init
Initialize a Symbiont-governed project. Creates agent definitions, Cedar policies, and configuration files. Use when setting up a new project with AI agent governance or adding Symbiont to an existing project.
symbi-policy
Create, edit, or validate Cedar authorization policies for Symbiont agents. Use when defining access control rules, setting up security policies, or debugging policy evaluation.
symbi-dsl
Parse, validate, and create Symbiont DSL agent definitions. Use when writing new agents, debugging DSL syntax errors, or understanding existing agent definitions.
symbi-verify
Verify MCP tool schemas using SchemaPin cryptographic verification. Use when adding new MCP servers, auditing existing tool integrations, or checking tool integrity.
symbi-audit
Query and analyze Symbiont's cryptographic audit logs. Use when reviewing agent activity, investigating incidents, or preparing compliance reports.