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/kryptobaseddev/cleo/docs-updategit clone --depth 1 https://github.com/kryptobaseddev/cleoWhat 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.00016 | $0.00544 |
| Opus 5 | $0.00008 | $0.00272 |
| Sonnet 5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
gsd:docs-update 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gsd:docs-update — 91% identical, 4 lines differ
What it actually says
Flag handling rule:
- The optional flags documented below are available behaviors, not implied active behaviors
- A flag is active only when its literal token appears in
$ARGUMENTS - If a documented flag is absent from
$ARGUMENTS, treat it as inactive --force: skip preservation prompts, regenerate all docs regardless of existing content or GSD markers--verify-only: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)- If
--forceand--verify-onlyboth appear in$ARGUMENTS,--forcetakes precedence
<execution_context> @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/workflows/docs-update.md </execution_context>
Available optional flags (documentation only — not automatically active):
--force— Regenerate all docs. Overwrites hand-written and GSD docs alike. No preservation prompts.--verify-only— Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the gsd-doc-verifier agent (Phase 4).
Active flags must be derived from $ARGUMENTS:
--forceis active only if the literal--forcetoken is present in$ARGUMENTS--verify-onlyis active only if the literal--verify-onlytoken is present in$ARGUMENTS- If neither token appears, run the standard full-phase generation flow
- Do not infer that a flag is active just because it is documented in this prompt
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.
- yesterday First seen · 49 lines · 16 tokens per session scan A eb89e1b7034f
gsd:docs-update is a command published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 11d ago), licensed MIT. It adds 16 tokens to every session and 544 once invoked, about $0.0001 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 commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.