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 Ezee234/symbi-gemini-cli --skill symbi-policygit clone --depth 1 https://github.com/Ezee234/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/ezee234/symbi-gemini-cli/symbi-policy)<a href="https://agentmods.dev/skills/ezee234/symbi-gemini-cli/symbi-policy"><img src="https://agentmods.dev/badge/skills/ezee234/symbi-gemini-cli/symbi-policy/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/ezee234/symbi-gemini-cli/symbi-policy"><img src="https://agentmods.dev/badge/skills/ezee234/symbi-gemini-cli/symbi-policy.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.00037 | $0.00344 |
| Opus 5 | $0.00018 | $0.00172 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
symbi-policy 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 10d 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.
This is a copy
100% identical to symbi-policy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Cedar Policy Management
Help the user create or modify Cedar policies for their Symbiont agents.
Cedar Policy Syntax Reference
Cedar policies use permit and forbid to control access:
// Allow an agent to read from a specific resource
permit(
principal == Agent::"data-analyzer",
action == Action::"read",
resource in ResourceGroup::"public-datasets"
);
// Forbid writing PII unless the agent has HIPAA compliance
forbid(
principal,
action == Action::"write",
resource
) when {
resource.contains_pii == true
} unless {
principal.compliance_level == "hipaa"
};
Common Policy Patterns
When asked to create a policy, identify the pattern:
- Role-based: Different agent roles get different permissions
- Resource-scoped: Permissions vary by resource type/sensitivity
- Time-bounded: Permissions that expire or are scheduled
- Approval-gated: Actions requiring human approval
- Audit-all: Log everything, permit/deny selectively
Workflow
- Ask what the policy should govern (which agents, which actions, which resources)
- Identify the pattern from the list above
- Write the Cedar policy
- Save to
policies/directory - If symbi is available, validate with
symbi dsl parseto check syntax
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.
- 10d ago First seen · 50 lines · 37 tokens per session scan A ada80c8d52c5
symbi-policy is a skill published in the GitHub repository Ezee234/symbi-gemini-cli (1 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 344 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to symbi-policy, differing in 0 lines, and is treated as a copy.
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.