Borrowing it
Nothing to install: this file belongs to yurakawa/mskills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yurakawa/mskills/main/.github/instructions/cli-commands.instructions.mdgit clone --depth 1 https://github.com/yurakawa/mskillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/yurakawa/mskills/cli-commands)<a href="https://agentmods.dev/instructions/yurakawa/mskills/cli-commands"><img src="https://agentmods.dev/badge/instructions/yurakawa/mskills/cli-commands/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/yurakawa/mskills/cli-commands"><img src="https://agentmods.dev/badge/instructions/yurakawa/mskills/cli-commands.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00426 | $0.00426 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
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 1mo 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.
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 ✓ symbolconsole.log(chalk.green(`✓ Skill '${name}' added`)); -
Errors: Use
chalk.red()with descriptive messagesconsole.error(chalk.red(`Error: ${error.message}`)); process.exit(1); -
Info: Use
chalk.cyan()for informational messages -
Spinners: Use
orafor long-running operationsconst 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*Commandfunction that takes aCommandinstance - 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
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.
- 1mo ago First seen · 73 lines · 426 tokens per session scan A 4bd76b0236ec
mskills cli-commands.instructions.md is an instructions file published in the GitHub repository yurakawa/mskills (3 stars, last pushed 6mo ago), licensed MIT. It adds 426 tokens to every session, about $0.0017 per session on Opus 5.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.
Other instructions, from other repositories
create-trimble-app typescript.instructions.md
Instructions for julianoczkowski/create-trimble-app, covering typescript patterns for modus components, event type casting, common event types, component ref types and modal ref pattern.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).