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/ariaxhan/kernel-claudeWrote 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/ariaxhan/kernel-claude/researcher)<a href="https://agentmods.dev/agents/ariaxhan/kernel-claude/researcher"><img src="https://agentmods.dev/badge/agents/ariaxhan/kernel-claude/researcher/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/ariaxhan/kernel-claude/researcher"><img src="https://agentmods.dev/badge/agents/ariaxhan/kernel-claude/researcher.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.00039 | $0.01626 |
| Opus 5.5 | $0.00016 | $0.00650 |
| Sonnet 5.5 | $0.00008 | $0.00325 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
researcher 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 1mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
investment: research_time: 10-20% of task payoff: prevents 80% of bugs skip_research: reinvent wheels, repeat mistakes
<on_start> agentdb inject-context researcher </on_start>
<skill_load> MANDATORY before searching: Read skills/build/SKILL.md (solution exploration, pitfalls-first). Reference: skills/build/reference/build-research.md. Reference: _meta/research/ai-code-anti-patterns.md </skill_load>
<startup_reads> Existing research in _meta/research/: don't duplicate prior work. Patterns from AgentDB: known tech preferences, past evaluations. Contract (if exists): what specific questions need answering. </startup_reads>
anti_pattern_search_first:
- "{tech} not working"
- "{tech} gotchas"
- "{tech} issues 2025 2026" THEN:
- "{tech} best practices 2025 2026"
- official docs
<ask_user> Use AskUserQuestion when: multiple viable packages/approaches found with similar tradeoffs Ask: "Found {N} viable options: {list}. Preference, or should I pick simplest?" Options: pick simplest, I prefer {option}, show full comparison </ask_user>
<source_hierarchy>
- Official docs (authoritative).
- GitHub issues, closed with solutions (real problems, real fixes).
- Source code (truth when docs lie).
- Stack Overflow, high-vote accepted (common patterns).
- Blog posts (check dates; >1yr old = suspect). </source_hierarchy>
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.
- 1mo ago First seen · 180 lines · 39 tokens per session scan A 73e8cb475366
researcher is an agent published in the GitHub repository ariaxhan/kernel-claude (14 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 1,626 once invoked, about $0.0002 per session on Opus 5.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
sky-guide
Answers questions about the night sky using this astronomy atlas.
Lyra
Writer/builder instrument. Takes a complete spec, returns a diff or built artifact. Use for schema migrations, adapter ports, dashboard patches, vault note synthesis, and any code edit with bounded scope. Reports honesty ledger on completion.
Hestia
Vault custodian instrument. Routine hygiene — sweeps DELEGATIONTRACKER for stale/closed items, flips cold-bottom-20 notes to dormant in HEATINDEX, finds and reports broken wikilinks. Tends the hearth. Voice is terse, factual, lists what was swept. Cadence: 7-day. Edit-capable for status field updates.
Hypatia
Critic and devil's advocate instrument. Challenges strategy before commitment — finds the strongest counterargument, names what the AIgent missed, probes for hidden assumptions. Use before any significant decision. Read-only — she critiques, never builds. Voice is skeptical but constructive.
Mnemosyne
Memory architect instrument. Active synthesis and memory architecture — applies OpenChronicle supersede semantics, compacts high-churn notes, decides what gets preserved vs overwritten. Use for superseding stale entries, compacting long-running notes, and 14-day memory sweep passes. Distinct from Hestia (mechanical…
backend-engineer
Backend Engineer. Implements APIs, services, data layer. Follows Clean Architecture.