argv-flag

Detect secret-bearing flags on command-line interfaces for security findings.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill argv-flag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: argv-flag
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packages/agentbundle/tests/fixtures/creds/skills/argv-flag
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill argv-flag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill models and tests a command-line workflow where sensitive credentials are passed as flags, helping you catch insecure token handling before it reaches production.

Core Features & Use Cases

  • Credentialed CLI Fixture: Represents a CLI that accepts a token argument on the command line for security validation scenarios.
  • Security Rule Coverage: Verifies that secret-bearing flags such as token, bearer, password, or PAT are rejected or flagged.
  • Use Case: Useful when evaluating agent behavior, CLI wrappers, or test harnesses that need to detect unsafe credential exposure on argv.

Quick Start

Ask the agent to inspect a credentialed CLI fixture and confirm that passing a token on the command line is treated as a security finding.

Frequently Asked Questions about argv-flag

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

FAQPage Schema
How do I detect secret tokens passed on the command line?▼

Detecting secret tokens passed on the command line requires deterministic parsing of arguments to identify and reject secret-bearing flags like token, bearer, or password, surfacing them as security findings.

What is an argv credential leak in CLI applications?▼

An argv credential leak in CLI applications occurs when sensitive credentials like tokens or passwords are passed as command-line arguments, exposing them to other processes and triggering security validation findings.

How do I test CLI wrappers for unsafe credential exposure?▼

Testing CLI wrappers for unsafe credential exposure involves applying a security validation fixture that inspects command-line arguments and explicitly rejects secret-bearing flags to surface AC26(b) findings.

Can I use argument parsing to flag insecure token handling in agent evaluations?▼

Yes, you can use deterministic argument parsing during agent evaluations to flag insecure token handling by verifying that secret-bearing flags such as tokens or PATs are explicitly rejected or flagged as findings.

What are the limitations of using command-line arguments for passing credentials?▼

The limitations of using command-line arguments for passing credentials include exposure to other processes, making secret-bearing flags like tokens or passwords insecure and requiring explicit rejection to prevent leaks.