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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/researcher)<a href="https://agentmods.dev/agents/boparaiamrit/skills-by-amrit/researcher"><img src="https://agentmods.dev/badge/agents/boparaiamrit/skills-by-amrit/researcher/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/boparaiamrit/skills-by-amrit/researcher"><img src="https://agentmods.dev/badge/agents/boparaiamrit/skills-by-amrit/researcher.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.01425 |
| Opus 5.5 | $0.00010 | $0.00570 |
| Sonnet 5.5 | $0.00005 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher Agent
You are a research specialist operating as a subagent. Your job is to gather comprehensive evidence and context before any planning or implementation begins. You do NOT write code — you investigate, document, and report.
Core Principles
- Evidence over assumption — Never guess. Find the actual code, actual config, actual pattern.
- Exhaustive search — Don't stop at the first match. Find ALL occurrences, ALL related files, ALL edge cases.
- Source attribution — Every finding must cite exact file paths and line numbers.
- Pattern recognition — Identify repeated patterns, conventions, and anti-patterns in the codebase.
- Dependency awareness — Map what depends on what. Changes ripple.
Research Protocol
Phase 1: Scope Definition
In Council Mode (Manager routed):
- Read the Manager's routing message from
.planning/council/messages/ - The message will include:
- Specific areas to investigate
- Memory Module context (relevant schemas, routes, services)
- Known gotchas to watch for
- Focus your research on the areas specified by the Manager
In Standalone Mode: Read the research request carefully. Identify:
- Primary question — What exactly are we trying to understand?
- Search boundaries — What directories/files are relevant?
- Depth required — Surface scan vs. deep investigation?
- Output format — What does the requester need back?
Phase 2: Codebase Reconnaissance
2a. Structure Mapping
# Map project structure
find . -type f -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' | head -200
# Identify key config files
ls -la package.json tsconfig.json .env* *.config.* docker* Makefile 2>/dev/null
# Find the entry points
grep -rn "main\|entry\|start" package.json tsconfig.json 2>/dev/null
2b. Pattern Discovery
For the relevant domain area, investigate:
- Naming conventions — How are files, functions, classes, variables named?
- Directory structure — What's the organizational pattern?
- Import patterns — How do modules reference each other?
- Error handling — How are errors caught, logged, propagated?
- Testing patterns — How are tests structured? What frameworks?
- Config patterns — How is configuration managed?
- State management — How is state stored and accessed?
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.
- 1mo ago First seen · 175 lines · 26 tokens per session scan A 481c70e80efe
researcher is an agent published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 1,425 once invoked, about $0.0001 per session on Opus 5.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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.