excrtx-govern-tools

Governs agent tool usage with classification policies, mandatory logging, and draft-first communication rules.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-govern-tools-elderbernardi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: excrtx-govern-tools
Source: https://github.com/elderbernardi/exocortex.saas/tree/main/skills/excrtx-govern-tools
Command: npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-govern-tools-elderbernardi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents can invoke tools that mutate state, send messages, or change configuration without oversight, causing irreversible damage or unauthorized communication. This Skill enforces a governance layer that classifies every tool call, mandates logging of destructive actions, and blocks unapproved external communication. ## Core Features & Use Cases - Tool Classification Policies: Categorizes tool calls into internal, research, external communication, and configuration types, each with a defined policy (free use, draft-first, or explicit approval). - Mandatory Logging & Failsafe: Requires every state-modifying tool call to be logged in a session log, and forces agents to report tool failures instead of silently retrying or inventing data. - Draft-First Communication: Distinguishes operational self-delivery to the executive from third-party communication, requiring draft approval before any external message is sent. - Isolated Config Validation: Provides a reference pattern using PATH shims and fake binaries to validate configuration mutations (e.g., hermes config set) without touching the main runtime. - Use Case: When an agent needs to push code, send an email, or install a package, this Skill forces it to classify the action, generate a draft for approval, log the operation, and refuse blacklisted commands like rm -rf. ## Quick Start Ask the agent to check how many skills are installed and the last modification date of FEATURES.md, and verify it uses real tools with logged, verifiable output instead of guessing.

Frequently Asked Questions about excrtx-govern-tools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control when an AI agent can use external tools?▼

Classify each tool call by type—internal, research, external communication, or configuration—and assign a policy to each. Internal tools run freely with logging, while external communication and configuration changes require draft-first or explicit approval.

What is draft-first approval for agent communication?▼

Draft-first requires the agent to generate any third-party message locally, present it to the executive, and send only after approval. Self-delivery to the executive's own home channel is exempt, but ambiguous recipients always require a draft.

How do I test configuration changes without affecting the main runtime?▼

Use an isolated validation pattern with a PATH shim: place a fake executable in a temporary directory that logs arguments, run the real script against it, and verify the exact calls emitted before integrating into setup scripts.

Which tool actions should be blacklisted for AI agents?▼

Blacklist irreversible or high-risk actions such as rm -rf on any path, system package installation via apt or brew, and sending messages to third parties without approval. These require explicit human authorization.

Why does datetime comparison fail in configuration smoke tests?▼

Comparing timezone-naive and timezone-aware datetimes raises an error. Treat timestamps without timezone info as explicit UTC using datetime.fromisoformat with a tzinfo fallback before comparing with datetime.now(timezone.utc).