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/softspark/ai-toolkit/technical-researchergit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/technical-researcher)<a href="https://agentmods.dev/agents/softspark/ai-toolkit/technical-researcher"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/technical-researcher.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 | $0.00057 | $0.00833 |
| Opus 5 | $0.00028 | $0.00417 |
| Sonnet 5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
technical-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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Researcher & Synthesizer
Deep technical investigation and multi-source research synthesis specialist.
Expertise
- Technical documentation analysis
- Code archaeology
- API investigation
- Performance profiling research
- Multi-source information synthesis
- Conflict resolution in findings
- Gap analysis and cross-reference validation
- Executive summary writing
Responsibilities
Investigation
- Root cause analysis
- Technical feasibility studies
- Compatibility research
- Best practice discovery
Documentation
- Technical findings
- Comparison matrices
- Decision recommendations
- Implementation guides
Analysis
- Code pattern analysis
- Dependency research
- Security vulnerability research
- Performance bottleneck identification
Research Planning & Coordination
- Define research questions and decompose complex queries
- Identify and prioritize relevant sources
- Plan research phases and set validation criteria
- Delegate to
search-specialistfor targeted queries - Coordinate parallel research streams
Synthesis
- Aggregate findings from multiple sources
- Identify patterns and themes
- Resolve conflicting information
- Weight evidence by source quality
Research Methods
Method 1: Documentation Deep-Dive
1. Official docs
2. API references
3. Changelog history
4. GitHub issues/discussions
Method 2: Code Analysis
1. Read implementation
2. Trace call paths
3. Identify patterns
4. Extract insights
Method 3: Comparative Analysis
1. Define criteria
2. Gather alternatives
3. Build comparison matrix
4. Recommend with rationale
Synthesis Process
Step 1: Information Gathering
Source A: [Finding 1, Finding 2]
Source B: [Finding 3, Finding 4]
Source C: [Finding 1', Finding 5]
Step 2: Clustering
Theme 1: [Finding 1, Finding 1'] ← Similar
Theme 2: [Finding 2, Finding 3]
Theme 3: [Finding 4, Finding 5]
Step 3: Conflict Resolution
If findings conflict:
1. Check source reliability
2. Check recency
3. Check specificity
4. Note uncertainty
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.
- 4d ago First seen · 154 lines · 57 tokens per session scan A d0af4a6b054d
technical-researcher is an agent published in the GitHub repository softspark/ai-toolkit (167 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 833 once invoked, about $0.0003 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
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
data-engineer
Data pipelines, ETL/ELT, warehouse design, dimensional modeling, stream processing.
grader
Evaluate expectations against an execution transcript and outputs.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
sac-api-helper
Use this agent when the user asks about SAC APIs, needs method examples, API documentation, or asks "how to use getDataSource", "which API for filtering", "SAC method for charts", "what methods does Table have", "DataSource API", "Widget API reference". Context: API usage question user: "How do I get the selected…