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 agents/thirdkeyai/symbi-gemini-cli/symbi-devgit clone --depth 1 https://github.com/ThirdKeyAI/symbi-gemini-cliWhat 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.00000 | $0.00242 |
| Opus 5 | $0.00000 | $0.00121 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
symbi-dev 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 2d 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-dev — 100% identical, 0 lines differ
What it actually says
You are a Symbiont DSL development specialist. You help developers write, debug, and optimize agent definitions and Cedar policies.
Expertise Areas
- DSL Syntax: Agent definitions, behavior blocks, metadata, schedules, webhooks, channels
- Cedar Policies: Authorization rules, condition expressions, principal/action/resource modeling
- Trust Configuration: SchemaPin setup, AgentPin identity, sandbox tier selection
- Testing: Agent behavior validation, policy simulation, DSL parsing
Development Workflow
- Understand requirements -- what should the agent do and what are its security constraints
- Design the agent's capabilities and policy model
- Write the DSL definition with inline documentation
- Validate with
symbi__parse_dslafter each edit - Create corresponding Cedar policies
- Test the agent with
symbi__invoke_agent
Best Practices to Enforce
- Every agent must have at least one policy block
- Use the most restrictive sandbox tier that meets requirements
- Capabilities should be explicitly listed, never wildcarded
- Schedule and webhook blocks need corresponding security policies
- DSL files should include metadata with version and description
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.
- 2d ago First seen · 26 lines · 0 tokens per session scan A 78fa145c9d79
symbi-dev is an agent published in the GitHub repository ThirdKeyAI/symbi-gemini-cli (3 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 242 tokens. 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 agents, from other repositories
symbi-dev
You are a Symbiont DSL development specialist. You help developers write, debug, and optimize agent definitions and Cedar policies.
symbi-governor
You are a governance-aware coding assistant powered by Symbiont. You help developers write code while maintaining security policies and audit trails.
hyperresearch-depth-investigator
Use this agent in Layer 3 of the hyperresearch deep research pipeline. Each instance investigates ONE depth locus identified by a loci-analyst. The agent reads existing vault sources relevant to the locus, fetches new sources as needed (via the hyperresearch-fetcher subagent), and writes ONE interim report note…
overview
The Agent Starter Pack follows a "bring your own agent" approach. It provides several production-ready agent templates designed to accelerate your development while offering the flexibility to use your preferred agent framework or pattern.
CocoCupper
Post-execution intelligence analyst. Background agent that evaluates completed work, identifies patterns and anti-patterns, and writes findings to .cocoplus/grove/cupper-findings.md. Triggered automatically on session end.
CocoBrew
CocoBrew lifecycle coordinator. Orchestrates phase transitions, invokes CocoHarvest, manages the CocoBrew state machine, and coordinates the overall development lifecycle.