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/kv-listnpx skills add KeyArgo/custodian-kernel --skill kv-listgit clone --depth 1 https://github.com/KeyArgo/custodian-kernelWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/keyargo/custodian-kernel/kv-list)<a href="https://agentmods.dev/skills/keyargo/custodian-kernel/kv-list"><img src="https://agentmods.dev/badge/skills/keyargo/custodian-kernel/kv-list.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00015 | $0.00308 |
| Opus 5 | $0.00008 | $0.00154 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
kv-list 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 5d 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
77% identical to slack-channel-list — 16 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
Kv List
List all keys in the Custodian KV store with optional prefix
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 kv-list --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.
- 5d ago First seen · 51 lines · 15 tokens per session scan A 28180ca3c991
kv-list is a skill published in the GitHub repository KeyArgo/custodian-kernel (118 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 308 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to slack-channel-list, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
Agent Memory
Give your agent persistent cross-session memory — recall what went wrong on similar tasks before starting, then capture whether the work succeeded or failed so repeated mistakes auto-promote into prevention rules. Runs locally via the ThumbGate MCP server (recall, capturefeedback, preventionrules, feedbackstats) — no…
thumbgate-feedback
Dual-write feedback to Amp MCP memory AND thumbgate for DPO export, analytics, and cross-platform portability.
thumbgate-feedback
Capture thumbs up/down feedback into structured memories and prevention rules. Use when user gives explicit quality signals about agent work (e.g. "that worked", "that failed", "thumbs up/down"). Do NOT use for general questions, code generation, file operations, or any task that is not explicit feedback on prior…
recall-context
Recall relevant past failures, prevention rules, and context packs before starting a coding task.
memory-sync
Review the auto-extracted candidates in .claude/memory/pending.md and commit keepers to the canonical memory files (landmarks.md, libraries.md, decisions.md, landmines.md, conventions.md, pending-questions.md, backlog.md). Invoke at session start when the SessionStart hook reports pending candidates, or any time…