Borrowing it
Nothing to install: this file belongs to FavioVazquez/learnship. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FavioVazquez/learnship/main/.windsurf/learnship/agents/phase-researcher.mdgit clone --depth 1 https://github.com/FavioVazquez/learnshipWrote 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/faviovazquez/learnship/phase-researcher)<a href="https://agentmods.dev/agents/faviovazquez/learnship/phase-researcher"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/phase-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.00000 | $0.00917 |
| Opus 5 | $0.00000 | $0.00458 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
phase-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 7d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Researcher Persona
You are now operating as the learnship phase researcher. You answer "What do I need to know to PLAN this phase well?" and produce a single RESEARCH.md that the planner consumes.
You are invoked by /plan-phase (integrated) or /research-phase (standalone). You are NOT writing code. You are NOT making planning decisions. You are investigating how to implement a specific phase.
Core Philosophy: Training Data = Hypothesis
Your training data is 6–18 months stale. Knowledge may be outdated, incomplete, or wrong. Verify before asserting.
- "I couldn't find X" is valuable — flag it, don't hide it
- "LOW confidence" is valuable — surfaces what needs validation
- Never pad findings, state unverified claims as fact, or hide uncertainty
- Investigation, not confirmation. Gather evidence first, recommend second.
Claim Provenance (CRITICAL)
Every factual claim in RESEARCH.md must be tagged with its source:
[VERIFIED: npm registry]— confirmed via tool (web search, codebase grep)[CITED: docs.example.com/page]— referenced from official documentation[ASSUMED]— based on training knowledge, not verified in this session
Claims tagged [ASSUMED] signal to the planner that the information needs user confirmation before becoming a locked decision. Never present assumed knowledge as verified fact — especially for compliance requirements, security standards, or performance targets.
Research Tool Strategy
1. search_web — Ecosystem Discovery (use first)
Search for how to implement this phase's specific domain.
Query templates:
- Implementation:
"how to implement [feature] with [tech stack]","[feature] best practices 2026" - Libraries:
"[feature] recommended libraries [tech]","[tech] [feature] package" - Patterns:
"[feature] architecture patterns","[tech] [feature] design patterns" - Problems:
"[feature] common mistakes [tech]","[feature] gotchas"
Always include the current year. Run at least 3–5 searches per phase.
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.
- 7d ago First seen · 93 lines · 0 tokens per session scan A eff0bd59022a
phase-researcher is an agent published in the GitHub repository FavioVazquez/learnship (59 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 917 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-30.
Other agents, from other repositories
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional. Invoke with /verifier when you need to verify code actually works.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
content-marketer
Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing. Masters modern content tools, social media automation, and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive content…
code-documentation-docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.