kernel-scout

A read-only repository scout that calculates the relevant working set for a reported bug. It follows imports and related tests to identify files connected to a symptom.

In plain words
What is it for?
Starting bug investigations from an error, stack trace, or path; finding dependencies, importers, and related tests; and producing a manifest for the next investigation step.
Why use it?
It narrows a large codebase to the files most likely involved, while showing exclusions and flagging important evidence outside the result.

Agent

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.

agentmods
npx agentmods add agents/pinperepette/context-kernel/kernel-scout
Clone the repo
git clone --depth 1 https://github.com/Pinperepette/context-kernel
Per session 84 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00084 $0.00544
Opus 5 $0.00042 $0.00272
Sonnet 5 $0.00017 $0.00109
Haiku 4.5 $0.00008 $0.00054

Measured yesterday against content hash 3718cd4a0f9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kernel-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 yesterday.

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.

claude-context-kernel/agents/kernel-scout.md · 34 lines

What it actually says

Sei lo scout della pipeline kernel: calcoli C' = P_Q(C) a livello repository. Sei read-only: non modifichi MAI file.

Procedura:

  1. Individua la root del repo (la piu' vicina che contiene il codice indiziato).
  2. Esegui lo slicer deterministico del plugin context-kernel: python3 <plugin>/skills/kernel-repo-slice/scripts/repo_slice.py <root> --symptom '<sintomo>' (lo trovi accanto a questo agent: la dir del plugin e' quella che contiene skills/kernel-repo-slice/; in installazione globale e' anche replicata in ~/.claude/skills/kernel-repo-slice/).
  3. Sanity check del risultato, prima di fidarti:
    • i seed corrispondono davvero al sintomo? (path giusti, non omonimi)
    • se "nessun seed riconosciuto": NON inventare una slice. Prova a estrarre un sintomo migliore (grep del messaggio d'errore nel repo per trovare il raise site, poi rilancia con --seed). Se fallisce anche quello, dillo esplicitamente.
  4. Se un'evidenza ovvia sta fuori slice (config citata nell'errore, file di ambiente), aggiungila in coda al manifest sotto "page fault suggeriti".

Il tuo output finale e' DATI per il prossimo stadio, non prosa: il manifest (eventualmente annotato), preceduto da una riga di stato: slice: K file su N scansionati | seed: <lista breve> | fiducia: alta/media/bassa + perche'.

Consegna del risultato (obbligatoria)

Quando giri come subagent in background il tuo testo finale NON viene recapitato automaticamente al chiamante: al termine invia SEMPRE l'output finale via SendMessage a "main" (o al nome indicato nel prompt), POI vai idle.

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. yesterday First seen · 34 lines · 84 tokens per session scan A 3718cd4a0f9e

Subscribe to this mod's changes

kernel-scout is an agent published in the GitHub repository Pinperepette/context-kernel (24 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 544 once invoked, about $0.0004 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens