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 commands/wyattjoh/skills/cli-flagsgit clone --depth 1 https://github.com/wyattjoh/skillsWhat 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.00000 | $0.02682 |
| Opus 5 | $0.00000 | $0.01341 |
| Sonnet 5 | $0.00000 | $0.00536 |
| Haiku 4.5 | $0.00000 | $0.00268 |
Grade A, and why
cli-flags 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 2d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
just — CLI flag reference
just is a single command with no subcommands. Every "mode" is a flag. This table
is transcribed from just --help on the pinned local binary, v1.57.0
(spellings, short forms, argument placeholders, and [env: ...] / [default: ...] /
[possible values: ...] annotations are authoritative). Explanations are drawn from
the just manual.
Source of truth: just --help (v1.57.0). The reviewed upstream manual snapshot also
contains newer, version-gated features; the binary wins when they disagree.
Invocation
just [OPTIONS] [ARGUMENTS]...
[ARGUMENTS]... — "Overrides and recipe(s) to run, defaulting to the first recipe in
the justfile." It carries VAR=value overrides, recipe names, and each recipe's own
arguments, in order.
Action flags (mode switches)
Listed under Commands: in the help. Several produce side effects — do not run
them blindly.
| Flag | Short | Arg | Purpose | Effect |
|---|---|---|---|---|
--list |
-l |
[<MODULE>...] |
List recipes in <MODULE> (root if omitted), with doc comments. |
read-only |
--summary |
Space-separated recipe names on one line. | read-only | ||
--groups |
List recipe groups (see [group(...)]). |
read-only | ||
--choose |
Pick recipe(s) via a chooser ($JUST_CHOOSER, default fzf). |
runs recipes | ||
--show |
-s |
<RECIPE_PATH>... |
Print a recipe's source. | read-only |
--usage |
<RECIPE_PATH>... |
Print usage info (args + doc) for a recipe. | read-only | |
--dump |
Print the parsed justfile. | read-only | ||
--json |
Print the justfile as JSON. | read-only | ||
--variables |
List variable names. | read-only | ||
--evaluate |
Print all variables and values; with a name arg, just that one. | read-only (runs backticks) | ||
--fmt |
Format and overwrite the justfile. | writes justfile | ||
--init |
Create a new justfile in the project root. | writes justfile | ||
--edit |
-e |
Open the justfile in $VISUAL/$EDITOR (falls back to vim). |
opens editor | |
--command |
-c |
<COMMAND>... |
Run an arbitrary command with the working dir, .env, overrides, and exports set. |
executes a command |
--clean |
[<RECIPE_PATH>...] |
Clear the recipe cache (optionally by path prefix). | mutates cache | |
--completions |
<SHELL> |
Print a completion script. [possible values: bash, elvish, fish, nushell, powershell, zsh] |
read-only | |
--changelog |
Print the changelog. | read-only | ||
--man |
Print the man page. | read-only |
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.
- 2d ago First seen · 147 lines · 0 tokens per session scan A 7a82eb4a9407
cli-flags is a command published in the GitHub repository wyattjoh/skills (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,682 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.