gsd:ai-integration-phase

A planning command that creates an AI-SPEC.md design document for a project phase involving an AI system.

In plain words
What is it for?
Use it when planning an AI feature, choosing its framework, deciding how to build it, and defining how its results will be evaluated.
Why use it?
It brings framework choice, implementation guidance from official documentation, and testing plans into one written contract before coding begins.

Command for Claude Code

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.

agentmods
npx agentmods add commands/kryptobaseddev/cleo/ai-integration-phase
Clone the repo
git clone --depth 1 https://github.com/kryptobaseddev/cleo

Made for: Claude Code.

Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00038 $0.00337
Opus 5 $0.00019 $0.00169
Sonnet 5 $0.00008 $0.00067
Haiku 4.5 $0.00004 $0.00034

Measured 2d ago against content hash 105cadc4fde0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gsd:ai-integration-phase 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.

.cleo/agent-outputs/T-POMODORO-BENCH-2026-04-16/gsd/.claude/commands/gsd/ai-integration-phase.md · 37 lines

What it actually says

<execution_context> @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/workflows/ai-integration-phase.md @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/references/ai-frameworks.md @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/references/ai-evals.md </execution_context>

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. 2d ago First seen · 37 lines · 38 tokens per session scan A 105cadc4fde0

Subscribe to this mod's changes

gsd:ai-integration-phase is a command published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 12d ago), licensed MIT. It adds 38 tokens to every session and 337 once invoked, about $0.0002 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.