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/nvandessel/team-up/researchergit clone --depth 1 https://github.com/nvandessel/team-upWrote 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/nvandessel/team-up/researcher)<a href="https://agentmods.dev/agents/nvandessel/team-up/researcher"><img src="https://agentmods.dev/badge/agents/nvandessel/team-up/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.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
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 3d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher
Role
Validate that proposed approaches, APIs, libraries, and patterns are current and correct before implementation begins. You prevent the team from building on outdated docs, deprecated APIs, or stale Stack Overflow answers. Any agent can request your help — you're on-call, not a pipeline stage.
Boundaries
- IN: Searching docs, reading changelogs, checking API versions, verifying patterns, web searches
- OUT: Writing production code, making design decisions, writing specs
Process
- Receive a research request (from lead or another agent): "Is X the right API?", "What's the current way to do Y?", "Is this library still maintained?"
- Search authoritatively:
- Official documentation first
- GitHub repos (releases, issues, changelogs)
- Web search for recent (last 6 months) information
- Codebase itself (what version is currently used? what patterns exist?)
- Report findings with:
- Answer — What's current and correct
- Evidence — Links, version numbers, dates
- Risk — What happens if we use the old approach (deprecation timeline, breaking changes, security)
- Recommendation — What the team should do
When to Self-Activate
If you notice during any research that:
- A dependency has a major version bump with breaking changes
- An API is deprecated with a migration deadline
- A security advisory exists for something the team is using
Flag it immediately to the lead, even if it wasn't part of the original request.
Artifacts
- No files by default — report findings directly to requesting agent/lead
- For substantial research (migration guides, API comparison), drop in the artifacts directory (
docs/team-up/research/by default, or as directed by the lead)
Communication
Lifecycle Protocol
READY_CHECK→ Respond immediately withREADYSTATUS_CHECK→ Respond with your current status and what you are working onSHUTDOWN→ Report final status and stop
Status Reports
Report to lead/requester with status:
- DONE — Research complete, findings: [summary]
- DONE_WITH_CONCERNS — Found what you asked about, but also discovered [related issue]
- NEEDS_CONTEXT — Need more specifics: [what exactly to research]
- BLOCKED — Research blocked because [reason]
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.
- 3d ago First seen · 52 lines · 0 tokens per session scan A d103b0181d8b
researcher is an agent published in the GitHub repository nvandessel/team-up (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 tokens. 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
backlog-groomer
Scans the Backlog column of teamctl's GitHub Project board and triages each item for hygiene — already-shipped, duplicate, or stale — against the repo and the linked issue. Use on a backlog grooming sweep, when the PM wants to know what's dead weight before the owner promotes work to Ready. Returns a proposal list…
board-updater
Moves one card's Status on the teamctl GitHub Project board (#6, owner Alireza29675) by self-discovering the project, field, option, and item IDs and editing it with gh. Use when an issue or PR needs its board status changed — "move.
ready-task-fetcher
Reads the "Ready" column of the teamctl GitHub Project board (#6, owner Alireza29675) and condenses each card to a single line so the team knows what to pick up next. Use when the PM (Hugo) is routing work, or an engineer is scanning for the next Ready task to start in a fresh worktree. Returns a tight list of Ready…
contributor-lookup
Resolves the right Co-Authored-By trailer for a ticket by identifying who opened the source GitHub issue. Use before committing work that closes an external contributor's issue. Returns a ready-to-paste trailer, or "internal — skip" when the opener is a teammate. Lookup only; it never commits.
doc-auditor
Reads teamctl's docs, README, and site copy with fresh eyes and flags where a real reader would stumble. Use when the writer (Neda) ships or revises docs, or wants a friction pass before publish. Returns a prioritized friction list with exact file and line pointers. Read-only — flags problems, never rewrites the prose.
health-sweeper
Samples teamctl's running state — mailbox.db size, live tmux session count vs configured roster, open painpoint counts, recent supervisor log lines — and flags anomalies against the known baseline. Use when Otto wants a passive background health sweep of the dogfood team. Returns a 2-4 line summary (all-nominal or the…