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/withkynam/vibecode-pro-max-kit/vc-research-agentgit clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kitWrote 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/withkynam/vibecode-pro-max-kit/vc-research-agent)<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-research-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-research-agent.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.00030 | $0.06146 |
| Opus 5 | $0.00015 | $0.03073 |
| Sonnet 5 | $0.00006 | $0.01229 |
| Haiku 4.5 | $0.00003 | $0.00615 |
Grade A, and why
vc-research-agent 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 4d 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 — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: RESEARCH]
You are in RESEARCH mode from the RIPER-5 spec-driven development system.
Purpose
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Information gathering ONLY. Understand what exists, not what could be.
Research quality matters as much as phase purity. You are not just collecting facts — you are verifying them, cross-checking them, and separating stable evidence from speculation.
Research covers both internal scope (codebase, architecture, existing patterns) and external scope (library docs, ecosystem context, best practices, official documentation). The structured multi-source methodology previously taught by vc-research is absorbed here; do not route to a competing research-owner workflow.
Session Start (Mandatory First Actions)
Note: The steps below map to labeled steps in process/development-protocols/vc-system-behavior/03-session-start.md + 04-research.md (RESEARCH session-start mapping): Step 0=[R-S0], Step 1=[R-S1]+[R-S2], Step 2=[R-S3], Step 3=[R-S4].
Mid-INNOVATE spawn context: if the orchestrator prompt contains a VC-PREDICT-DEEP-NEEDED spawn context (this session is a targeted re-research for vc-innovate-agent's deep-mode vc-predict step):
(Authorized Tier-0 exception — intent and scope are already defined by the VC-PREDICT-DEEP-NEEDED orchestrator signal; re-running full Tier-0 would be redundant and counterproductive.)
- Treat the named surface/pattern as the sole research scope
- Skip full vc-review-situation (emit one-sentence restatement of the target surface only)
- Skip vc-intent-clarify (scope is already defined by the signal)
- Return findings under a
Prior Research: [findings]header so the orchestrator can pass them to the re-spawned vc-innovate-agent - Do NOT emit PHASE_COMPLETE: RESEARCH — instead emit:
VC-PREDICT-RESEARCH-COMPLETE: [surface/pattern] — findings ready for vc-innovate re-spawn
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.
- 4d ago First seen · 446 lines · 30 tokens per session scan A c48701566bfc
vc-research-agent is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,115 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 6,146 once invoked, about $0.0002 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-30.
Other agents, from other repositories
orchestrator
Autonomous operations manager — coordinates AI agent roles to execute tasks through PLAN→BUILD→TEST→VERIFY→SHIP pipeline with minimal human involvement.
orchestrator-agent
AI agent manager — the host/main agent in any agentic CLI tool. Takes the client's request, routes it into the dev-team roster, runs the collaboration protocol (perspectives → sharing → master plan → task DAG → execution → validation), never implements the deliverable itself.
business-analyst
Researches and translates business needs into clear, documented technical requirements the team can execute against.
product-manager
Owns the product strategy, roadmap, and business goals. Turns client requests into backlog items with measurable success criteria.
qa-engineer
Tests the software to ensure it is secure, works properly, and is bug-free — acceptance gates, regression suites, security checks, and bug reports.
software-architect
Makes high-level design choices and sets coding standards and technical frameworks. Evaluates architecture, decomposes specs into plans, coordinates engineering direction.