authenticate

Copy an agent lock file to authenticate guarded operations.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill authenticate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authenticate
Source: https://github.com/Kord96/kordinate/tree/main/shared/skills/authenticate
Command: npx skills add https://github.com/Kord96/kordinate --skill authenticate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authenticate before performing guarded operations. Copy the agent's lock file, do work, remove it.

Core Features & Use Cases

  • Ensures per-task access control by copying and removing a per-agent lock file to a temporary location.
  • Applies across agents like charon and augur, using the runtime lock cache to guard sensitive tasks.
  • Provides a simple cleanup step to avoid leaving authentication artifacts behind.

Quick Start

Authenticate once per task by capturing the agent's lock file from the runtime cache, perform the guarded operations, and remove the token when finished.

Frequently Asked Questions about authenticate

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

FAQPage Schema
How do I authenticate an agent before performing guarded operations?

To authenticate before performing guarded operations, you copy the agent's lock file from the runtime cache into a temporary location, use it for your work, and remove it afterwards to ensure per-task access control.

What is a per-task lock token used for in runtime-agent contexts?

A per-task lock token is used to guard sensitive tasks across runtime-agent contexts like charon and augur, ensuring authenticated access control by requiring the agent's lock file during execution.

Do I need to clean up the lock file after completing guarded tasks?

Yes, you need to clean up the lock file after completing guarded tasks by removing the copied token from its temporary location, which provides a simple cleanup step to avoid leaving authentication artifacts behind.

Can I use this authentication approach with agents like charon and augur?

Yes, this authentication approach applies across agents like charon and augur, utilizing the runtime lock cache to guard sensitive tasks by capturing and managing the per-agent lock file during execution.

What's the best way to handle per-task access control for sensitive operations?

The best way to handle per-task access control is to capture the agent's lock file from the runtime cache, perform the guarded operations using that token, and remove it when finished to maintain security.

Why does my agent need a lock file from the runtime cache for guarded operations?

Your agent needs a lock file from the runtime cache to authenticate before performing guarded operations, ensuring that sensitive tasks require proper access control via a per-task lock token during execution.