Vibeos Local Audit

Read local vibeos-policy tool audit without telemetry.

Skill metadata

Source	Bundled (installed by default)
Path	skills/devops/vibeos-local-audit
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	audit, hooks, policy, security, observability
Related skills	cursor-capabilities-bridge, mcp-safe-hygiene, vibeos-ops-health

Reference: full SKILL.md

信息

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

VibeOS Local Audit

Inspect Cursor-hook-style local tool auditing from vibeos-policy. Nothing leaves the machine — no analytics backends.

When to Use

• User asks what tools ran, how long, or whether a push was blocked
• After enabling vibeos-policy / Day-12 observability work
• Debugging “did the agent call X?”

Prerequisites

• Plugin installed: examples/plugins/vibeos-policy/ → ~/.vibeos/plugins/
• vibeos plugins enable vibeos-policy
• Log path: $VIBEOS_HOME/logs/vibeos-policy-audit.jsonl

How to Run

vibeos vibeos-policy summary --limit 200
vibeos vibeos-policy tail -n 30
# or:
tail -n 40 ~/.vibeos/logs/vibeos-policy-audit.jsonl

Coding profile uses its own VIBEOS_HOME — set it first if needed.

Quick Reference

Event type	Meaning
tool	One tool call (name, duration_ms, redacted previews, ok)
session_summary	Rollup on session end (top tools, fail count)

Env	Effect
VIBEOS_POLICY_AUDIT=0	Blocks stay; no log writes
VIBEOS_POLICY_DISABLE=1	Off entirely
VIBEOS_POLICY_ALLOW_GITHUB=1	Allow push/PR this process

Procedure

1. Confirm plugin enabled (vibeos plugins / config plugins.enabled).
2. Run any agent turn that uses tools.
3. vibeos vibeos-policy summary — check tools / fail.
4. For a blocked push, look for ok: false and args mentioning git push.
5. Do not paste raw audit lines into chat if they might still hold paths the user considers sensitive — summarize counts instead.

Pitfalls

• Audit is process-local JSONL — rotate/truncate manually if huge
• Redaction is best-effort (PEM, sk-, ghp_, key=value) — not a vault
• Mid-session plugin enable needs a new process to load hooks
• Never ship this log to a third-party “observability product” plugin

Verification

• After a chat with tools: audit file grows
• summary shows non-empty tools
• git push without opt-in → block message + failed/blocked audit line