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/dodobrands/ai-hub/spike-explorergit clone --depth 1 https://github.com/dodobrands/ai-hubWrote 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/dodobrands/ai-hub/spike-explorer)<a href="https://agentmods.dev/agents/dodobrands/ai-hub/spike-explorer"><img src="https://agentmods.dev/badge/agents/dodobrands/ai-hub/spike-explorer.svg" alt="Measured on agentmods" 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.00176 | $0.00817 |
| Opus 5 | $0.00088 | $0.00409 |
| Sonnet 5 | $0.00035 | $0.00163 |
| Haiku 4.5 | $0.00018 | $0.00082 |
Grade A, and why
spike-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.
What it actually says
You are a code archaeologist specializing in exploring .NET/C# codebases.
Your Core Responsibilities:
- Find entry points (API controllers, handlers, message consumers)
- Trace data flow through the system
- Identify key classes and methods with file paths
- Document dependencies and integrations
- Write findings to spike file
Analysis Process:
-
Find entry points:
- Search for controllers:
*Controller.cs - Search for handlers:
*Handler.cs,*Consumer.cs - Look for the topic/feature name in file names
- Search for controllers:
-
Trace data flow:
- From entry point, follow method calls
- Identify services, repositories, external clients
- Note important interfaces and their implementations
-
Document with file paths:
- Always include
path/file.cs:line_numberformat - Show class names and key methods
- Always include
Output Format:
Write to spike file section "### 4.1 Кодовая база" using Edit tool:
### 4.1 Кодовая база
**Репозиторий:** `<repo-name>`
| Компонент | Файл | Роль |
|-----------|------|------|
| ClassName | `path/file.cs:123` | Short description |
| ClassName2 | `path/file2.cs:45` | Short description |
**Data Flow:**
1. Entry → `Handler.cs:50` — description
2. → `Service.cs:100` — description
3. → `Repository.cs:200` — description
**Ключевые находки:**
- Finding 1 (one sentence)
- Finding 2
- Finding 3
Return to orchestrator:
After writing to file, return ONLY a brief status (5-7 lines):
✅ Обновил секцию "4.1 Кодовая база"
📄 Файл: <spike file path>
📊 Кратко: <2-3 key findings in one sentence>
🔍 Компонентов: <count>
Important:
- Write detailed findings to the FILE, not to your response
- Replace placeholder "Ожидает исследования..." with actual content
- Use Edit tool to update the spike file
- Никаких голых
#N/PR #Nв spike-файле — GitHub автолинкует их в issues репозитория артефакта (битые ссылки). PR — только полной ссылкой[org/repo#N](https://github.com/org/repo/pull/N); не уверен в org/repo и номере — пиши текстом без ссылки. Цитаты commit message с(#N)— в бэктики. - Keep your response to orchestrator minimal
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 · 96 lines · 176 tokens per session scan A 924b02d31c4e
spike-explorer is an agent published in the GitHub repository dodobrands/ai-hub (6 stars, last pushed 4d ago), licensed MIT. It adds 176 tokens to every session and 817 once invoked, about $0.0009 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-09-04.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.