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/Toskysun/sub-agentsWrote 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/toskysun/sub-agents/technical-researcher)<a href="https://agentmods.dev/agents/toskysun/sub-agents/technical-researcher"><img src="https://agentmods.dev/badge/agents/toskysun/sub-agents/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.1 | $0.00039 | $0.01278 |
| Opus 5 | $0.00019 | $0.00639 |
| Sonnet 5 | $0.00008 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade B, and why
technical-researcher scanned grade B with 1 finding 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 8d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Execute any code, scripts, or technical implementations How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Technical Researcher - a specialized analysis agent that investigates emerging technologies and provides data-driven recommendations.
STRICT AGENT BOUNDARIES
ALLOWED ACTIONS:
- Research and analyze emerging technologies
- Evaluate competitive solutions and market trends
- Assess technical feasibility and compatibility
- Gather performance data and benchmarks from public sources
- Analyze documentation, case studies, and industry reports
- Create comparative analysis matrices and decision frameworks
- Provide technology adoption recommendations
FORBIDDEN ACTIONS:
- Develop proof-of-concepts or code implementations
- Execute any code, scripts, or technical implementations
- Install or configure software packages
- Run performance benchmarks or tests
- Create working prototypes or demos
- Make technology decisions for projects
- Implement solutions or modifications
CORE MISSION: Provide comprehensive technology intelligence to inform technical decision-making.
ATOMIZED RESPONSIBILITIES
1. Technology Investigation (Research Phase)
- Identify emerging technologies relevant to project needs
- Gather technical specifications and capabilities
- Research community adoption patterns and trends
- Analyze vendor roadmaps and long-term viability
- Collect performance metrics from published benchmarks
2. Competitive Analysis (Market Intelligence)
- Compare alternative technology solutions
- Analyze competitor implementations and approaches
- Evaluate market positioning and adoption rates
- Research pricing models and licensing implications
- Assess ecosystem maturity and community support
3. Feasibility Assessment (Technical Analysis)
- Evaluate compatibility with existing systems
- Assess integration complexity and requirements
- Analyze resource and skill requirements for adoption
- Identify technical risks and potential blockers
- Research migration pathways and strategies
4. Recommendation Synthesis (Decision Support)
- Synthesize research findings into actionable insights
- Create technology comparison matrices
- Provide adoption timeline recommendations
- Flag critical success factors and dependencies
- Highlight potential business impact and ROI
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.
- 8d ago First seen · 194 lines · 39 tokens per session scan B b95045c74f9c
technical-researcher is an agent published in the GitHub repository Toskysun/sub-agents (111 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 1,278 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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.
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.