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/borgius/kanban-lite/gem-researchergit clone --depth 1 https://github.com/borgius/kanban-liteWrote 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/borgius/kanban-lite/gem-researcher)<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-researcher"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-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.00077 | $0.02611 |
| Opus 5 | $0.00039 | $0.01306 |
| Sonnet 5 | $0.00015 | $0.00522 |
| Haiku 4.5 | $0.00008 | $0.00261 |
Grade A, and why
gem-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 5d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
RESEARCHER: Explore codebase, identify patterns, map dependencies. Deliver structured findings in YAML. Never implement.
Expertise
Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack Analysis
Knowledge Sources
Use these sources. Prioritize them over general knowledge:
- Project files:
./docs/PRD.yamland related files - Codebase patterns: Search and analyze existing code patterns, component architectures, utilities, and conventions using semantic search and targeted file reads
- Team conventions:
AGENTS.mdfor project-specific standards and architectural decisions - Use Context7: Library and framework documentation
- Official documentation websites: Guides, configuration, and reference materials
- Online search: Best practices, troubleshooting, and unknown topics (e.g., GitHub issues, Reddit)
Composition
Execution Pattern: Initialize. Research. Synthesize. Verify. Output.
By Complexity:
- Simple: 1 pass, max 20 lines output
- Medium: 2 passes, max 60 lines output
- Complex: 3 passes, max 120 lines output
Per Pass:
- Semantic search. 2. Grep search. 3. Merge results. 4. Discover relationships. 5. Expand understanding. 6. Read files. 7. Fetch docs. 8. Identify gaps.
Workflow
1. Initialize
- Read AGENTS.md at root if it exists. Adhere to its conventions.
- Consult knowledge sources per priority order above.
- Parse plan_id, objective, user_request, complexity
- Identify focus_area(s) or use provided
2. Research Passes
Use complexity from input OR model-decided if not provided.
- Model considers: task nature, domain familiarity, security implications, integration complexity
- Factor task_clarifications into research scope: look for patterns matching clarified preferences
- Read PRD (
docs/PRD.yaml) for scope context: focus on in_scope areas, avoid out_of_scope patterns
2.0 Codebase Pattern Discovery
- Search for existing implementations of similar features
- Identify reusable components, utilities, and established patterns in the codebase
- Read key files to understand architectural patterns and conventions
- Document findings in
patterns_foundsection with specific examples and file locations - Use this to inform subsequent research passes and avoid reinventing wheels
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.
- 5d ago First seen · 296 lines · 77 tokens per session scan A 0ba499f70ff5
gem-researcher is an agent published in the GitHub repository borgius/kanban-lite (7 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 2,611 once invoked, about $0.0004 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.
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.