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/getklai/klai/autogit clone --depth 1 https://github.com/GetKlai/klaiWhat 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.03408 |
| Opus 5 | $0.00029 | $0.01704 |
| Sonnet 5 | $0.00012 | $0.00682 |
| Haiku 4.5 | $0.00006 | $0.00341 |
Grade A, and why
auto scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Voor backend-only endpoints: test direct met curl: How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/klai:auto — Klai Autonomous Pipeline
Input: $ARGUMENTS (SPEC-ID verplicht, bijv. SPEC-KB-003)
Pre-execution git context:
!git branch --show-current 2>/dev/null
!git status --porcelain 2>/dev/null | head -10
Doel
Voer de complete post-SPEC cyclus volledig autonoom uit. Geen menselijke goedkeuring vereist. De enige bewuste stop in de totale workflow is de SPEC-goedkeuring in de plan-fase — die heeft de gebruiker al gedaan.
Flags:
--no-e2e: Sla E2E tests over (bijv. als dev server niet draait)--no-merge: Stop na sync + E2E, merge niet automatisch--issue: Maak alleen op expliciet verzoek een gekoppeld publiek GitHub Issue--review: Voeg twee menselijke goedkeuringsstops toe (na interview review + voor merge)
Volledige flow (geen --review):
run → interview-standard auto-fix → migraties → sync --pr → e2e → merge
Met --review:
run → [STOP: interview review] → migraties → sync --pr → e2e → [STOP: finale gate] → merge
Phase 0: SPEC Verificatie
Lees de SPEC in docs/specs/{SPEC-ID}/spec.md of docs/specs/{SPEC-ID}.md
(of .workflow/specs/{SPEC-ID}/spec.md) om te bevestigen dat de SPEC bestaat.
Als de SPEC niet bestaat: geef een foutmelding en stop.
Bepaal:
spec_title: de titel van de SPECbranch_name:feature/{SPEC-ID}review_mode: true als--reviewvlag aanwezighas_e2e: true tenzij--no-e2evlag aanwezig
Phase 1: Implementatie
Implementeer de SPEC direct: lees de acceptance criteria, maak de code- en testwijzigingen, en draai de relevante test- en lintcommando's tot ze slagen.
Als er na implementatie nog test failures of build errors zijn:
- Delegeer aan
expert-debugsubagent met de exacte foutmelding - Verifieer dat de fix de tests laat slagen
- Herhaal tot alle tests groen zijn (max 10 iteraties)
- Na 10 iteraties zonder succes: rapporteer wat er nog openstaat en stop
Dit is hetzelfde gedrag als tijdens normale coding — build breekt, fix, herhaal.
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 · 370 lines · 58 tokens per session scan A f3377e38d44e
auto is a command published in the GitHub repository GetKlai/klai (11 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 3,408 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.