secure-skill-runtime

Enforce runtime security for agent skills with provenance tracking and no-go repo management.

3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill secure-skill-runtime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secure-skill-runtime
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/secure-skill-runtime
Command: npx skills add https://github.com/dvy1987/agent-loom --skill secure-skill-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runtime security for agent skills — prevents state corruption, skill overwrite attacks, denial of service, and enforces provenance tracking and no-go repo management. Load as part of the secure-* skill sequence whenever an agent processes external content or writes to the skill store. Also load when the user asks to check for state corruption, prevent skill overwrite, manage no-go repos, check provenance, audit runtime security, detect DoS patterns, or protect the skill store.

Core Features & Use Cases

  • Self-Protection: Modified only by human commits; runs in sequence with other secure-* skills.
  • Provenance & No-Go: Maintains provenance records and a no-go repo list to block untrusted sources.
  • DoS & Integrity: Enforces resource limits and validation to prevent exploitation.

Quick Start

Load as part of the secure-* skill sequence to enforce runtime security whenever processing external content.

Frequently Asked Questions about secure-skill-runtime

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

FAQPage Schema
How do I prevent skill overwrite attacks when processing external content?

Prevent skill overwrite attacks by loading a runtime security guard that enforces explicit human approval for external changes before any content persists to the skill store, ensuring only validated commits modify skills.

What is provenance tracking for agent skills and when do I need it?

Provenance tracking for agent skills records the origin and approval history of external content. You need it whenever an agent processes external content or writes to the skill store to ensure only approved sources persist.

How do I block untrusted repositories from writing to the agent skill store?

Block untrusted repositories using automated no-go repo management, which maintains a blocked source list and validates content origins during runtime security audits to prevent untrusted sources from persisting.

Does runtime security for agent skills detect denial of service patterns?

Runtime security for agent skills detects denial of service patterns by enforcing resource limits and validation during external content processing, preventing state corruption and exploitation through automated checks.

Can I audit runtime security and check for state corruption in my agent skills?

You can audit runtime security and check for state corruption by loading the security guard during provenance checks, which validates that only approved content persists and flags any unauthorized modifications.

What are the limitations of using a runtime security guard for agent skills?

The runtime security guard requires loading as part of a secure-* skill sequence and depends on explicit human approval for external changes, meaning automated workflows may pause for validation during skill store writes.