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 skills/keyargo/custodian-kernel/docker-logsnpx skills add KeyArgo/custodian-kernel --skill docker-logsgit clone --depth 1 https://github.com/KeyArgo/custodian-kernelWhat 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.00310 |
| Opus 5 | $0.00008 | $0.00155 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
docker-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 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.
This is a copy
89% identical to docker-list — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Docker Logs
Tail the last N lines of a Docker container's stdout log
Authority band
This tool runs under L0 authority in the Custodian kernel. Read-only; no real-world effects — always autonomous.
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
| (see execute.py for full schema) |
Configuration
No additional configuration required — uses credentials already wired to Custodian.
Usage
custodian tools run docker-logs --param value
Custodian governance
Every call to this tool passes through the Custodian kernel authority check before executing. The kernel verifies the current authority band, checks spending caps where applicable, logs the action to the OCSF audit trail, and escalates to a human operator if the action exceeds the declared band.
Adding this tool to any Hermes agent session requires no code changes —
declare custodian-band: L0 in the SKILL.md frontmatter and the kernel
wraps it automatically.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 51 lines · 16 tokens per session scan A 12ba01c29319
docker-logs is a skill published in the GitHub repository KeyArgo/custodian-kernel (118 stars, last pushed 11d ago), licensed MIT. It adds 16 tokens to every session and 310 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to docker-list, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
gnt-check-action
Check a side-effectful action against this organization's approved gnt rules before taking it, and stop on a blocked or needshuman verdict.
dev-standards
Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.
dep-updates
Plan and apply Go dependency updates, including advisory-driven bumps, Trivy/govulncheck validation, and supply-chain review. Use when the user asks to update dependencies, refresh modules for security alerts, or run dependency vulnerability scans.
repro
Turn a bug symptom into a structured, reproducible bug report — summary, environment, exact repro steps, actual vs expected, and evidence (logs, error text, failing route/test) — and then optionally scaffold a failing regression test that pins it. Use this the moment a bug, defect, crash, 500, wrong count, broken…
agt-policy-authoring
Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.
write-unit-tests
Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.