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/github-commentnpx skills add KeyArgo/custodian-kernel --skill github-commentgit 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.00014 | $0.00326 |
| Opus 5 | $0.00007 | $0.00163 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
github-comment 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
78% identical to discord-webhook — 14 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
Github Comment
Add a comment to a GitHub issue or pull request
Authority band
This tool runs under L1 authority in the Custodian kernel. Trivial autonomous spend or free side-effect — no human approval required.
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
| (see execute.py for full schema) |
Configuration
Set the required environment variables before use. Until configured, custodian tools run github-comment returns a stub response indicating which variables are needed.
Usage
custodian tools run github-comment --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: L1 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 · 14 tokens per session scan A 3cd7279bfcb2
github-comment is a skill published in the GitHub repository KeyArgo/custodian-kernel (118 stars, last pushed 10d ago), licensed MIT. It adds 14 tokens to every session and 326 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to discord-webhook, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
compliance-scan
Scans a Python AI project for EU AI Act compliance gaps using AIR Blackbox. Use when the user asks to check compliance, scan their code, audit their AI project, or mentions EU AI Act, Articles 9-15, or compliance checking.
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.
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual-mandate: spec coverage audit + deep bug finding.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
aget-file-issue
File issues with L520 governance compliance.