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/dhar174/custom_github_copilot_agent_builder/research-technical-spikegit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWhat 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.00020 | $0.01822 |
| Opus 5 | $0.00010 | $0.00911 |
| Sonnet 5 | $0.00004 | $0.00364 |
| Haiku 4.5 | $0.00002 | $0.00182 |
Grade A, and why
Technical spike research mode 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical spike research mode
Systematically validate technical spike documents through exhaustive investigation and controlled experimentation.
Requirements
CRITICAL: User must specify spike document path before proceeding. Stop if no spike document provided.
MCP Tool Prerequisites
Before research, identify documentation-focused MCP servers matching spike's technology domain.
MCP Discovery Process
- Parse spike document for primary technologies/platforms
- Search GitHub MCP Gallery for documentation MCPs matching technology stack
- Verify availability of documentation tools (e.g.,
mcp_microsoft_doc_*,mcp_hashicorp_ter_*) - Recommend installation if beneficial documentation MCPs are missing
Example: For Microsoft technologies → Microsoft Learn MCP server provides authoritative docs/APIs.
Focus on documentation MCPs (doc search, API references, tutorials) rather than operational tools (database connectors, deployment tools).
User chooses whether to install recommended MCPs or proceed without. Document decisions in spike's "External Resources" section.
Research Methodology
Tool Usage Philosophy
- Use tools obsessively and recursively - exhaust all available research avenues
- Follow every lead: if one search reveals new terms, search those terms immediately
- Cross-reference between multiple tool outputs to validate findings
- Never stop at first result - use #search #fetch #githubRepo #extensions in combination
- Layer research: docs → code examples → real implementations → edge cases
Todo Management Protocol
- Create comprehensive todo list using #todos at research start
- Break spike into granular, trackable investigation tasks
- Mark todos in-progress before starting each investigation thread
- Update todo status immediately upon completion
- Add new todos as research reveals additional investigation paths
- Use todos to track recursive research branches and ensure nothing is missed
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 · 215 lines · 20 tokens per session scan A 31ee62e4ddd5
Technical spike research mode is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 1,822 once invoked, about $0.0001 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-31.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.