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/callmetechie/fleet-manager/compose-logsgit clone --depth 1 https://github.com/CallMeTechie/fleet-managerWhat 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.00013 | $0.00513 |
| Opus 5 | $0.00006 | $0.00257 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
compose-logs 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.
What it actually says
Compose Logs
set -euo pipefail
source "${CLAUDE_PLUGIN_ROOT:-plugin}/commands/_compose-lib.sh"
TAIL=100; PROJECT=""; SERVER_ARG=""
set -f # no globbing of unquoted $ARGUMENTS (review H2)
# shellcheck disable=SC2086 # intentional: split ARGUMENTS into positional params
set -- ${ARGUMENTS:-}
while [ $# -gt 0 ]; do
case "$1" in
--tail) shift; TAIL="${1:-100}" ;;
--tail=*) TAIL="${1#*=}" ;;
--*) echo "Unknown flag: $1" >&2; exit 1 ;;
*) if [ -z "$SERVER_ARG" ]; then SERVER_ARG="$1"; else PROJECT="$1"; fi ;;
esac
shift
done
# If only one positional was given, it is the project (active server assumed).
if [ -n "$SERVER_ARG" ] && [ -z "$PROJECT" ]; then PROJECT="$SERVER_ARG"; SERVER_ARG=""; fi
[ -n "$PROJECT" ] || { echo "Usage: /compose-logs [server] <project> [--tail N]" >&2; exit 1; }
[[ "$PROJECT" =~ ^[A-Za-z0-9_.-]+$ ]] || { echo "Invalid project name" >&2; exit 1; }
[[ "$TAIL" =~ ^[0-9]+$ ]] || { echo "Invalid --tail" >&2; exit 1; }
NAME="$(resolve_server "$SERVER_ARG")"
build_ssh "$NAME"; echo_target "$NAME"
resolve_docker_cmd "$NAME"; docker_precheck
ENTRY="$(compose_find_project "$PROJECT")"
[ -n "$ENTRY" ] || { echo "ERROR: project '$PROJECT' not found in compose ls." >&2; exit 1; }
CF="$(echo "$ENTRY" | jq -r '.ConfigFiles')"
CFG_ARGS="$(compose_config_args "$CF")"
# shellcheck disable=SC2086 # CFG_ARGS is validated (no spaces in paths); intentional split into -f args
"${FM_SSH[@]}" "$FM_DOCKER compose $CFG_ARGS logs --tail $TAIL"
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 · 43 lines · 13 tokens per session scan A c0f27d646f7b
compose-logs is a command published in the GitHub repository CallMeTechie/fleet-manager (1 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 513 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-31.
Other commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
cleanup
Clean up TTS cache files to free up disk space.
deps-age
Analyze dependency freshness and maintenance activity.
review-pr
Comprehensive PR review checklist to ensure code quality, testing, and best practices.
release-prep
Automated release readiness validation.