flag-add

flag-add is a skill for Claude Code, Codex from zakelfassi/skills-driven-development. It costs 58 tokens per session (928 once invoked), scanned A, original, MIT.

A procedure for adding a command-line option to shipctl, including its parser definition, help text, shell completions, documentation, and tests. A command-line option is a setting users pass when starting a terminal command.

In plain words
What is it for?
Use it when adding or extending a shipctl flag, such as an output-directory option, or when adding an option to a subcommand.
Why use it?
It reduces the chance that an option works in the program but is missing from help, documentation, completions, or tests.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when adding or extending a shipctl flag, such as an output-directory option, or when adding an option to a subcommand.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zakelfassi/skills-driven-development/flag-add
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.

Any agent
npx skills add zakelfassi/skills-driven-development --skill flag-add
Clone the repo
git clone --depth 1 https://github.com/zakelfassi/skills-driven-development

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for flag-add

README.md
[![agentmods](https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/flag-add/github.svg)](https://agentmods.dev/skills/zakelfassi/skills-driven-development/flag-add)
Your own site
<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/flag-add"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/flag-add/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.

agentmods 80×15 button for flag-add

Your own site · 80×15
<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/flag-add"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/flag-add.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 928 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00058 $0.00928
Opus 5.5 $0.00023 $0.00371
Sonnet 5.5 $0.00012 $0.00186
Haiku 4.5 $0.00006 $0.00093

Measured 1mo ago against content hash ff79c3b4bf22, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flag-add 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.

examples/cli-tool/skills/flag-add/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flag Add

Add a new CLI flag to a shipctl command end-to-end.

Inputs

  • Command path (e.g., release, build cross, config set)
  • Flag name (long form, e.g., --output-dir)
  • Short alias (optional, e.g., -o)
  • Type (string, bool, integer, path)
  • Default value (or required if mandatory)
  • Description (one-line, used in help text and docs)

Steps

  1. Define the flag in the parser

    For Rust + clap:

    // In the relevant Args struct (src/cmd/{command}.rs)
    #[arg(long, short = '{alias}', default_value = "{default}",
          help = "{description}")]
    pub {flag_name}: {type},
    

    For Go + cobra:

    // In the relevant command file (cmd/{command}.go)
    cmd.Flags().{TypeVar}(&opts.{FlagName}, "{flag-name}", {default}, "{description}")
    
  2. Wire the value into the command logic Pass the flag value through to whatever downstream call needs it. Verify the happy path compiles: cargo check / go build ./....

  3. Update the help text Run shipctl {command} --help and confirm the flag appears with the correct description and default.

  4. Add shell completions Regenerate completions (invoke manpage-sync skill, or manually):

    shipctl completions bash > completions/shipctl.bash
    shipctl completions zsh  > completions/_shipctl
    shipctl completions fish > completions/shipctl.fish
    

    Commit the updated completion files.

  5. Update documentation Edit docs/reference/{command}.md:

    • Add a row to the Flags table: | --{flag-name} | {type} | {default} | {description} |
    • Add an Examples entry if the flag has a non-obvious use
  6. Write or extend a test

    // tests/cmd_{command}.rs
    #[test]
    fn test_{flag_name}_flag() {
        let output = Command::cargo_bin("shipctl").unwrap()
            .arg("{command}")
            .arg("--{flag-name}").arg("{test-value}")
            .assert().success();
        // assert output contains expected value
    }
    

Read the full file on GitHub · 93 lines

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. 1mo ago First seen · 93 lines · 58 tokens per session scan A ff79c3b4bf22

Subscribe to this mod's changes

flag-add is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 928 once invoked, about $0.0002 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-30.