trust

Manage user-level security grants for autonomous loops and repository shell gates.

36|2|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/alicicek/tale-mode --skill trust-alicicek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trust
Source: https://github.com/alicicek/tale-mode/tree/main/plugins/tale-mode/skills/trust
Command: npx skills add https://github.com/alicicek/tale-mode --skill trust-alicicek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a secure, user-controlled mechanism to authorize tale-mode's autonomous loop and repository-specific gates, preventing unauthorized code execution while maintaining a strict security posture.

Core Features & Use Cases

  • Gate Authorization: Manage the committed-gate trust store to verify repository-specific shell scripts before execution.
  • Environment Opt-in: Enable the autonomous loop on platforms like Codex by explicitly opting into root directory resolution.
  • Use Case: When you need to enable the autonomous loop for a new project or verify the safety of a repository's gate configuration, use this skill to understand the required manual security steps.

Quick Start

Ask the trust skill to explain how to authorize a new repository gate or enable the autonomous loop on your current platform.

Frequently Asked Questions about trust

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

FAQPage Schema
How do I authorize repository shell gates for autonomous loops?

Authorize repository shell gates by manually verifying content-hashes and adding them to the committed-gate trust store to ensure safe agentic execution. This user-controlled process prevents unauthorized code execution while maintaining a strict security posture for your autonomous loops.

What is a tale-mode gate and when do I need to verify its content-hash?

A tale-mode gate is a repository-specific shell script barrier requiring manual content-hash verification before autonomous execution. You need to verify it when enabling autonomous loops for a new project to ensure the gate configuration is safe and explicitly authorized by the user.

How do I enable the autonomous loop on Codex using root directory opt-in?

Enable the autonomous loop on Codex by explicitly opting into root directory resolution through a manual environment opt-in process. This user-level security grant ensures safe agentic execution by requiring strict adherence to user-only file creation protocols before activating the loop.

Can an agent modify security configurations when managing tale-mode opt-ins?

No, an agent cannot modify security configurations because managing tale-mode opt-ins requires strict adherence to user-only file creation protocols. This prevents unauthorized agent-driven security modifications and ensures all gate authorizations and environment opt-ins remain explicitly user-controlled.

What's the best way to securely manage tale-mode gates across multiple projects?

Securely manage tale-mode gates across multiple projects by using a committed-gate trust store to verify repository-specific shell scripts before execution. This approach ensures safe agentic execution by requiring manual verification of content-hashes and project-root opt-ins for each new repository.

Why does autonomous code execution require manual security grants?

Autonomous code execution requires manual security grants to prevent unauthorized code execution while maintaining a strict security posture. By facilitating manual verification of content-hashes and project-root opt-ins, the system ensures safe agentic execution remains explicitly user-controlled rather than agent-driven.