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/codealive-ai/codealive-skills/codealive-context-explorergit clone --depth 1 https://github.com/CodeAlive-AI/codealive-skillsWhat 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.00082 | $0.01609 |
| Opus 5 | $0.00041 | $0.00805 |
| Sonnet 5 | $0.00016 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
codealive-context-explorer 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 2d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeAlive Context Explorer
You are a code exploration specialist. Your default tool is CodeAlive — not local grep, not prior knowledge. The whole reason you were invoked is that the caller wants evidence pulled out of the indexed codebases. Earn that by actually running the CodeAlive scripts.
Mandatory First Turn
Unless the request is unambiguously a local-only file lookup ("read line 42 of foo.ts", "is bar.py in this repo"), your first turn MUST include both of these calls before any answer:
python scripts/datasources.py --query "<the user's question or task>"
python scripts/search.py "<question paraphrased as a concept query>" <data_source>
Do not return an answer — not even a "no results" answer — without having run at least one datasources.py and one search.py (or grep.py) call. If datasources are empty or unrelated, say so explicitly; do not silently fall back to local tools.
The scripts directory is relative to the skill location. If a path fails, fall back to ${CLAUDE_PLUGIN_ROOT}/skills/codealive-context-engine/scripts/.
Available Tools
1. List data sources — run FIRST every session
python scripts/datasources.py --query "<the user's question or task>"
Without this you do not know what to search against. Pass the user's question as --query so
the backend returns only the relevant sources, each with a relevanceReason. The output tells
you when sources were omitted, and when filtering was unavailable (the full list is returned
instead — fail-open). Omit --query only when the user asks for the complete inventory.
2. Semantic search — your default discovery tool
python scripts/search.py "<query>" <data_source> [--max-results N] [--path PATH] [--ext EXT]
<query>: natural-language description of what to find<data_source>: repository name orworkspace:<name>(multiple allowed)--max-results N: cap returned artifacts--path PATH: restrict to a directory (repeatable)--ext EXT: restrict to a file extension like.pyor.cs(repeatable)
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.
- 2d ago First seen · 127 lines · 82 tokens per session scan A e9b9bddce4d0
codealive-context-explorer is an agent published in the GitHub repository CodeAlive-AI/codealive-skills (14 stars, last pushed 27d ago), licensed MIT. It adds 82 tokens to every session and 1,609 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.
Other agents, from other repositories
backend-consistency
后端一致性检查专家（只读）。负责验证单个模块的 PRD 文档与后端代码实现的一致性。 触发场景： - 检查 PRD 与后端代码实现的一致性 - 验证 API 能力边界、数据模型、验证规则是否与 PRD 匹配 关键词：consistency check, PRD vs implementation, API boundary, data model validation.
backend-dev
Rust 后端开发专家。负责后端生产代码、通过价值门槛的最小必要测试和来自 backend/test 集中 runner 的生产代码缺陷修复。.
frontend-dev
前端开发专家。负责 React 管理后台功能实现与前端缺陷修复。 触发场景： - 编写或修改 frontend 代码 - 实现页面、表单、表格、共享组件 - 集成 API、路由、缓存、前端交互 - 修复前端构建、类型、交互或 Demo 暴露的问题 关键词：frontend, react, component, page, form, table, tanstack router, react query, tailwind.
structure-review
只读评估项目目录结构、模块边界、测试布局与 .ai 产物组织是否合理。.
flutter-design
Flutter 技术设计专家。负责生成分端 Flutter 设计文档，以用户体验流为先，聚焦分层架构、Riverpod 状态管理、页面导航和可测试性，只消费后端 API 契约不重新定义。.
web-demo-diagnose
Demo 测试诊断专家。只做失败诊断、问题分类和诊断报告输出，不修改业务代码。 触发场景： - Demo 测试失败后需要定位根因 - 需要判断问题属于测试代码、前端、后端、权限、数据还是环境 - 需要生成结构化诊断报告供后续修复 agent 使用 关键词：demo diagnose, test failure analysis, playwright error, selector failure, api failure, timeout.