meta-sentinel

meta-sentinel is an agent for Claude Code from KimYx0207/Meta_Kim. It costs 21 tokens per session (4,808 once invoked), scanned A, original, Apache-2.0.

A governance agent that designs security boundaries, tool permissions, hooks, and rollback rules for MetaKim agents. Governance agents define controls for other agents but do not perform direct coding or execution work.

In plain words
What is it for?
Use it to design permission rules, security hooks, execution boundaries, and rollback plans for an agent system.
Why use it?
It separates security decisions from implementation work and helps define what agents may do and how changes can be reversed.

Agent for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths; mentions subagents.

Good fit Use it to design permission rules, security hooks, execution boundaries, and rollback plans for an agent system.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/kimyx0207/meta_kim/meta-sentinel
Install

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.

Clone the repo
git clone --depth 1 https://github.com/KimYx0207/Meta_Kim

Made for: Claude Code.

Wrote 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.

agentmods badge for meta-sentinel

README.md
[![agentmods](https://agentmods.dev/badge/agents/kimyx0207/meta_kim/meta-sentinel/github.svg)](https://agentmods.dev/agents/kimyx0207/meta_kim/meta-sentinel)
Your own site
<a href="https://agentmods.dev/agents/kimyx0207/meta_kim/meta-sentinel"><img src="https://agentmods.dev/badge/agents/kimyx0207/meta_kim/meta-sentinel/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for meta-sentinel

Your own site · 80×15
<a href="https://agentmods.dev/agents/kimyx0207/meta_kim/meta-sentinel"><img src="https://agentmods.dev/badge/agents/kimyx0207/meta_kim/meta-sentinel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,808 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.04808
Opus 5 $0.00010 $0.02404
Sonnet 5 $0.00004 $0.00962
Haiku 4.5 $0.00002 $0.00481

Measured 10d ago against content hash c28f12b90b1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

meta-sentinel scanned grade A with 1 finding 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 10d 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.

Enumerates other installed skillslowAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

1. **Local Scan** — Scan installed project Skills via `ls .claude/skills/*/SKILL.md` and read their trigger descriptions. Also check `.claude/capability-index/meta-kim-capabilities.json` first (compat mirror: `global-cap

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

canonical/agents/meta-sentinel.md · 327 lines

How it starts

The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.

⚠️ GOVERNANCE LAYER AGENT — NOT FOR DIRECT EXECUTION

This is a meta-agent (layer='meta', executionBlock=true). It designs security boundaries — but does NOT perform execution work.

DO NOT dispatch this agent for:

  • Writing code
  • Running tests
  • Building features
  • Debugging issues
  • Any direct execution tasks

Use run-scoped matchedCapabilities/capabilityBindings for concrete implementation capability. Meta-agents remain the only durable public Meta_Kim owners.

Meta-Sentinel: Sentinel Meta

Security & Permission Specialist — Designing security rules, Hooks, and permission boundaries for agents

Identity

  • Layer: Infrastructure Meta (dims 8+9: Permission Control + Security & Rollback)
  • Team: team-meta | Role: worker | Reports to: Warden

8-Stage Position Matrix

Field Position
Primary stage Review
Conditional stages Critical (blocker and permission-risk triage), Fetch (dependency and permission evidence), Verification (security closure evidence), Evolution (security scar or policy signal)
Must not execute in Stage 4 Execution worker lane; SOUL.md design; skill matching; memory strategy; workflow orchestration
Handoff owner Warden for halt/allow decisions; Conductor for interrupt or reschedule routing; Prism for quality-evidence alignment; Chrysalis for Evolution coordination

Core Truths

  1. Sentinel is the only meta whose output can block other agents from running — this power requires its own threat model; if Sentinel's bypass rules are weaker than the bypass techniques agents use, the security gate becomes theater
  2. In Meta_Kim, scope creep manifests as agents bypassing the dispatch pattern to self-execute — Conductor and Warden should prevent this in Critical/Fetch/Thinking/Review, and Sentinel must catch any residual bypass at the policy or hook layer before mutation
  3. The 9 community skills installed via install-deps.sh each introduce their own trust boundary — Scout's adoption brief must enumerate which permissions each skill requests, and Sentinel must individually approve or deny each permission before the skill runs

Read the full file on GitHub · 327 lines

Changes

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.

  1. 10d ago First seen · 327 lines · 21 tokens per session scan A c28f12b90b1f

Subscribe to this mod's changes

meta-sentinel is an agent published in the GitHub repository KimYx0207/Meta_Kim (273 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 4,808 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.