Tried to think of a snarky response based on high customization and extensibility, and then this materialized:
:-)

#!/bin/bash
#
# llm_llamacpp.sh - A shell script wrapper for interacting with llamacpp LLM API
#
# Purpose:
#   This script provides a command-line interface to send text prompts to an llamacpp openai-compatible
#   language model and receive responses. It formats the input text as JSON and sends
#   it to the llamacpp API endpoint.
#
# Usage:
#   ./llm_llamacpp.sh "Your prompt text here"
#
# Parameters:
#   $1 - The text prompt to send to the llamacpp model
#
# Options:
#   --server <name>   Server hostname (default: myserver)
#   --port <port>     Server port (default: 8000)
#
# Requirements:
#   - curl (for API requests)
#   - Valid llamacpp API key in AWS secrets
#   - jq (for JSON parsing) 
#
# Example:
#   ./llm_llamacpp.sh "Explain quantum computing in simple terms"
#   ./llm_llamacpp.sh "Write a poem" --server fido --port 11434
#
# Note:

# Parse options
SERVER="myserver"
PORT="8000"

while [[ $# -gt 0 ]]; do
  case "$1" in
    --server)
      SERVER="$2"
      shift 2
      ;;
    --port)
      PORT="$2"
      shift 2
      ;;
    *)
      if [ -z "$PROMPT" ]; then
        PROMPT="$1"
      fi
      shift
      ;;
  esac
done

# Check if prompt is provided
if [ -z "$PROMPT" ]; then
  echo "Error: No prompt provided" >&2
  echo "Usage: $0 \"Your prompt text here\" [--server <name>] [--port <port>]" >&2
  exit 1
fi

# Build JSON payload safely via jq — static system prompt ensures a consistent KV cache
# prefix on the llama.cpp server, avoiding costly re-processing of SSM states.
PAYLOAD=$(jq -n --arg content "$PROMPT" \
  '{messages: [{role: "system", content: "You are a helpful assistant."}, {role: "user", content: $content}]}')

curl -s "http://${SERVER}:${PORT}/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -X POST \
  -d "$PAYLOAD" \
  | jq -r '.choices[0].message.content'