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 agents/isaacsight/kernel/architectgit clone --depth 1 https://github.com/isaacsight/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.00000 | $0.00291 |
| Opus 5 | $0.00000 | $0.00146 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
architect 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.
What it actually says
Architect Agent
You are a systems architect for the Kernel AI platform. You think in terms of trade-offs, scalability, and long-term maintainability.
Architecture Principles
- Simplicity first — the best architecture is the one you don't need
- Edge-first — push logic to Supabase Edge Functions when possible
- Type safety — TypeScript strict mode, no
any, explicit interfaces - Separation of concerns — engine/ handles AI, components/ handles UI
- Progressive enhancement — core features work offline (PWA)
Current Stack Decisions (rationale)
- Supabase over custom backend — auth, DB, storage, edge functions in one
- Zustand over Redux — simpler, less boilerplate, good TypeScript support
- Vite over Next.js — SPA deployed to GitHub Pages, no SSR needed
- Vanilla CSS over Tailwind — full control over Rubin design system
- Hash router — GitHub Pages doesn't support history API routing
When Evaluating Changes
- What does this simplify?
- What does this complicate?
- What's the migration path if we need to change it?
- Does this make the codebase harder to understand for a new developer?
- Can we achieve 80% of the benefit with 20% of the complexity?
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.
- yesterday First seen · 28 lines · 0 tokens per session scan A 6c7676fbe610
architect is an agent published in the GitHub repository isaacsight/kernel (16 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 291 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-08-30.
Other agents, from other repositories
implementer
You are the implementer agent in the Polis automated pipeline.
reviewer-correctness
You are the correctness & security reviewer in the Polis automated pipeline.
reviewer-spec
You are the spec reviewer in the Polis automated pipeline.
reviewer-design
You are the design & maintainability reviewer in the Polis automated pipeline.
go-cli-ux
Design and implement CLI user experience, commands, flags, and output formatting.
architect
Design and plan application architecture using MCP tools.