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.
npx agentmods add skills/zakelfassi/skills-driven-development/flag-addnpx skills add zakelfassi/skills-driven-development --skill flag-addgit clone --depth 1 https://github.com/zakelfassi/skills-driven-developmentWhat 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 | $0.00058 | $0.00928 |
| Opus 5 | $0.00029 | $0.00464 |
| Sonnet 5 | $0.00012 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
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 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.
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
requiredif mandatory) - Description (one-line, used in help text and docs)
Steps
-
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}") -
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 ./.... -
Update the help text Run
shipctl {command} --helpand confirm the flag appears with the correct description and default. -
Add shell completions Regenerate completions (invoke
manpage-syncskill, or manually):shipctl completions bash > completions/shipctl.bash shipctl completions zsh > completions/_shipctl shipctl completions fish > completions/shipctl.fishCommit the updated completion files.
-
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
- Add a row to the Flags table:
-
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 }
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.
- 3d ago First seen · 93 lines · 58 tokens per session scan A ff79c3b4bf22
flag-add is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 928 once invoked, about $0.0003 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-30.
Other skills, from other repositories
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
bigquery-ai-ml
Leverages BigQuery's built-in machine learning and GenAI capabilities for advanced data analytics. Use when you need to write SQL queries that perform time-series forecasting, predict values, detect outliers or anomalies, find key drivers, perform semantic search or vector search, classify text, calculate similarity…
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn"…
app-marketing-context
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.