Symbiont
PassAudited by ClawScan on May 10, 2026.
Overview
This appears to be a purpose-aligned local governance and skill-scanning helper, but users should review its external Symbiont install and local audit/policy files before relying on its security guarantees.
Before installing, decide whether you want this skill to constrain agent actions through local policies. Review the external symbi package source, inspect generated .symbiont policies and audit files, and do not rely on the claimed cryptographic audit coverage unless you verify the runtime support is actually installed and working.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may refuse or modify requested actions when local policies or verification checks say they are unsafe.
The persona intentionally makes policy checks authoritative over later user requests. This is disclosed and aligned with governance, but users should understand it can change agent behavior.
You do not bypass policy checks, even if the user asks you to.
Install this only if you want governance controls, and review the SOUL file and local policies so the refusal behavior matches your needs.
You are trusting the external Symbiont package source in addition to the skill files shown here.
The main runtime is an external package installed from a Homebrew tap, with alternative cargo/Docker install paths. That is expected for this integration, but the installed binary is outside the reviewed artifact contents.
brew tap thirdkeyai/tap && brew install symbi
Review the Homebrew formula/source repository, pin versions where possible, and verify signatures or checksums if available.
Local audit files may reveal what tools were blocked or reviewed, and audit summaries depend on those files remaining accurate.
The guard persists audit entries to a project-local JSONL file. Persistent audit context is purpose-aligned, but it can store operational history and can be misleading if later edited.
echo "$entry" >> "$AUDIT_DIR/tool-usage.jsonl"
Keep .symbiont/audit files protected, review them before sharing a repository, and clear or rotate them if they contain sensitive activity history.
You might assume stronger audit or enforcement coverage than is demonstrated by the included files alone.
The README advertises broad cryptographic audit coverage and references helper scripts such as audit-log.sh, while the provided manifest only includes the scanner and policy guard scripts. This is not evidence of malicious behavior, but users should verify the actual installed tooling before relying on those guarantees.
Cryptographic audit trails: JSONL logging of all state-modifying tool calls
Confirm that the external symbi runtime or any missing helper scripts are installed and functioning before depending on this for compliance or security enforcement.