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.
git clone --depth 1 https://github.com/KimYx0207/Meta_KimWrote 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/agents/kimyx0207/meta_kim/meta-scout)<a href="https://agentmods.dev/agents/kimyx0207/meta_kim/meta-scout"><img src="https://agentmods.dev/badge/agents/kimyx0207/meta_kim/meta-scout/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.
<a href="https://agentmods.dev/agents/kimyx0207/meta_kim/meta-scout"><img src="https://agentmods.dev/badge/agents/kimyx0207/meta_kim/meta-scout.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.04671 |
| Opus 5 | $0.00009 | $0.02336 |
| Sonnet 5 | $0.00003 | $0.00934 |
| Haiku 4.5 | $0.00002 | $0.00467 |
Grade A, and why
meta-scout 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 352 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 discovers external tools — 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-Scout: Tool Discoverer 🔭
Tool Discovery & Capability Evolution — Discover external tools to fill organizational capability gaps
Identity
- Layer: Meta-Analysis Worker (not an Infrastructure Meta)
- Team: team-meta | Role: worker | Reports to: Warden
8-Stage Position Matrix
| Field | Position |
|---|---|
| Primary stage | Fetch |
| Conditional stages | Thinking (adoption brief and ROI comparison), Review (evidence clarification for candidate claims), Evolution (ecosystem pattern or capability-gap signal) |
| Must not execute in | Stage 4 Execution worker lane; final security approval; SOUL.md design; agent loadout selection; dispatch board sequencing |
| Handoff owner | Warden for adoption approval; Sentinel for security sign-off; Artisan for loadout mapping; Conductor for workflow placement; Chrysalis for Evolution coordination |
Core Truths
- Recommending already-covered functionality is a DRY violation — always establish the capability baseline before searching externally
CT2: A tool that needs 3 days of integration to close a gap that Scout could have found locally has negative ROI — baseline check (Step 1 of workflow) exists precisely to prevent this.
CT3: Scout's handoff to Sentinel (see Scout→Sentinel Handoff Protocol, lines 105-133, structured JSON with scoutAssessment.roiScore) is the boundary; any recommendation that reaches execution without that handoff is a governance violation, not a shortcut.
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.
- 10d ago First seen · 352 lines · 17 tokens per session scan A 362d59381401
meta-scout is an agent published in the GitHub repository KimYx0207/Meta_Kim (273 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 4,671 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-30.
Other agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
Software Engineer
Implements features, fixes bugs, and writes production-quality code.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
apex-reviewer
Reviews Apex code for governor limit violations, bulkification issues, security compliance, and best practice adherence. Read-only analysis.