analyze

analyze is a command for Claude Code from isaacsight/kernel. It costs 0 tokens per session (173 once invoked), scanned A, original, MIT.

A command that reviews a project's structure, agent system, frontend routes, backend functions, dependencies, and TypeScript health, then reports architectural findings.

In plain words
What is it for?
Use it to inspect source files, components, routes, agents, engine code, Supabase edge functions, package dependencies, and compiler errors.
Why use it?
It gives developers a broad view of how the project is organized and highlights issues such as dead code, missing types, bundle size, or incomplete services.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to inspect source files, components, routes, agents, engine code, Supabase edge functions, package dependencies, and compiler errors.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/isaacsight/kernel/analyze
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/isaacsight/kernel

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 analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/isaacsight/kernel/analyze/github.svg)](https://agentmods.dev/commands/isaacsight/kernel/analyze)
Your own site
<a href="https://agentmods.dev/commands/isaacsight/kernel/analyze"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/analyze/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 analyze

Your own site · 80×15
<a href="https://agentmods.dev/commands/isaacsight/kernel/analyze"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 173 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00173
Opus 5.5 $0.00000 $0.00069
Sonnet 5.5 $0.00000 $0.00035
Haiku 4.5 $0.00000 $0.00017

Measured 2mo ago against content hash 059b86a42d56, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze 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 2mo 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.

.claude/commands/analyze.md · 15 lines

What it actually says

Analyze the Kernel project architecture and provide insights.

Steps:

  1. Read the project structure: find src/ -type f -name "*.ts" -o -name "*.tsx" | head -50
  2. Check component count: find src/components -type f | wc -l
  3. Check route structure in src/router.tsx
  4. Analyze the agent system in src/agents/ and src/engine/
  5. Check Supabase edge functions: ls supabase/functions/
  6. Review package.json for dependency health
  7. Run npx tsc --noEmit 2>&1 | tail -5 to check type health
  8. Provide a high-level architecture summary with recommendations

Focus areas: bundle size, dead code, missing types, agent system health, Supabase function coverage.

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. 2mo ago First seen · 15 lines · 0 tokens per session scan A 059b86a42d56

Subscribe to this mod's changes

analyze is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 173 tokens. 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-09-03.

Related

analyze compared with commands from other repositories

analyze next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
analyzeisaacsight/kernelCommand161mo agoMITA0Claude Code
investigate-sentry-issuedesplega-ai/agent-swarmCommand1.0kyesterdayMITA10Claude Code
unicli-repairolo-dot-io/Uni-CLICommand2283d agoApache-2.0A0Claude Code
kf-supportinclusionAI/AvernetCommand601yesterdayApache-2.0A26Claude Code
qa-changesOpenHands/extensionsCommand176yesterdayMITA63Claude Code
http-serviceMadAppGang/magusCommand14yesterdayMITA27Claude Code
doctorfatihkan/badiCommand71mo agoMITA0Claude Code