mskills cli-commands.instructions.md

mskills cli-commands.instructions.md is an instructions file for GitHub Copilot from yurakawa/mskills. It costs 426 tokens per session, scanned A, original, MIT.

A set of instructions for building command-line commands with Commander.js, a JavaScript library for defining terminal commands.

In plain words
What is it for?
Use it when adding commands to a Node.js command-line program, including arguments, options, colored feedback, spinners, and error handling.
Why use it?
It gives developers consistent rules for command structure, success and error messages, and handling long-running work.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/yurakawa/mskills/cli-commands
Clone the repo
git clone --depth 1 https://github.com/yurakawa/mskills

Made for: GitHub Copilot.

Per session 426 This file is loaded in full into every session.
When invoked 426 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00426 $0.00426
Opus 5 $0.00213 $0.00213
Sonnet 5 $0.00085 $0.00085
Haiku 4.5 $0.00043 $0.00043

Measured 3d ago against content hash 4bd76b0236ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mskills cli-commands.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/cli-commands.instructions.md · 73 lines

What it actually says

CLI Command Instructions

Command Structure

All commands follow a consistent pattern using Commander.js:

import type { Command } from 'commander';
import chalk from 'chalk';

export function registerCommandName(program: Command) {
  program
    .command('command-name')
    .description('Brief description')
    .argument('[arg]', 'Argument description')
    .option('-f, --flag', 'Option description')
    .action(async (arg, options) => {
      try {
        // Implementation
        console.log(chalk.green('✓ Success message'));
      } catch (error: any) {
        console.error(chalk.red(`Error: ${error.message}`));
        process.exit(1);
      }
    });
}

User Feedback

  • Success: Use chalk.green() with ✓ symbol

    console.log(chalk.green(`✓ Skill '${name}' added`));
    
  • Errors: Use chalk.red() with descriptive messages

    console.error(chalk.red(`Error: ${error.message}`));
    process.exit(1);
    
  • Info: Use chalk.cyan() for informational messages

  • Spinners: Use ora for long-running operations

    const spinner = ora('Processing...').start();
    // do work
    spinner.succeed('Done');
    

Error Handling

  • Always wrap command logic in try-catch blocks
  • Exit with code 1 on errors: process.exit(1)
  • Display user-friendly error messages, not stack traces

Command Registration

  • Export a register*Command function that takes a Command instance
  • All command registrations are imported and called in commands/index.ts
  • Use descriptive command names that match CLI usage

Testing Commands

  • Mock chalk, ora, and file system operations
  • Test both success and error paths
  • Verify correct exit codes on errors
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 73 lines · 426 tokens per session scan A 4bd76b0236ec

Subscribe to this mod's changes

mskills cli-commands.instructions.md is an instructions file published in the GitHub repository yurakawa/mskills (3 stars, last pushed 4mo ago), licensed MIT. It adds 426 tokens to every session, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.