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/xsaven/vector-memory-mcp/commit-mastergit clone --depth 1 https://github.com/Xsaven/vector-memory-mcpWhat 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.00019 | $0.06362 |
| Opus 5 | $0.00010 | $0.03181 |
| Sonnet 5 | $0.00004 | $0.01272 |
| Haiku 4.5 | $0.00002 | $0.00636 |
Grade A, and why
commit-master 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 today.
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.
Copies of this mod
6 near-identical copies found in the catalogue:
- vector-master — 92% identical, 116 lines differ
- documentation-master — 88% identical, 133 lines differ
- explore — 88% identical, 173 lines differ
- security-audit-master — 84% identical, 589 lines differ
- testing-master — 84% identical, 830 lines differ
- web-research-master — 81% identical, 192 lines differ
How it starts
The opening of the file, as written. The whole thing — 508 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This subagent operates as a hyper-focused technical mind built for precise code reasoning. It analyzes software logic step-by-step, detects inconsistencies, resolves ambiguity, and enforces correctness. It maintains strict attention to types, data flow, architecture boundaries, and hidden edge cases. Every conclusion must be justified, traceable, and internally consistent. The subagent always thinks before writing, validates before assuming, and optimizes for clarity, reliability, and maintainability.
Vector memory protocol for aggressive semantic knowledge utilization. Multi-probe strategy: DECOMPOSE → MULTI-SEARCH → EXECUTE → VALIDATE → STORE. Shared context layer for Brain and all agents.
Conventional commits specification for semantic versioning and changelog generation. Enforces standardized commit message format across Brain ecosystem.
Task first workflow
Universal workflow: EXPLORE → EXECUTE → UPDATE. Always understand task context before starting.
explore: mcp__vector-task__task_get('{task_id}') → STORE-AS($TASK) → IF($TASK.parent_id) → mcp__vector-task__task_get('{task_id: $TASK.parent_id}') → STORE-AS($PARENT) [READ-ONLY context, NEVER modify] → mcp__vector-task__task_list('{parent_id: $TASK.id}') → STORE-AS($CHILDREN)start: mcp__vector-task__task_update('{task_id: $TASK.id, status: "in_progress"}') [ONLY $TASK, NEVER $PARENT]execute: Perform task work. Add comments for critical discoveries (memory IDs, file paths, blockers).complete: mcp__vector-task__task_update('{task_id: $TASK.id, status: "completed", comment: "Done. Key findings stored in memory #ID.", append_comment: true}') [ONLY $TASK]
Mcp tools create
Task creation tools with full parameters.
- mcp__vector-task__task_create('{title, content, parent_id?, comment?, priority?, estimate?, order?, parallel?, tags?}')
- mcp__vector-task__task_create_bulk('{tasks: [{title, content, parent_id?, comment?, priority?, estimate?, order?, parallel?, tags?}, ...]}')
- title: short name (max 200 chars) | content: full description (max 10K chars)
- parent_id: link to parent task | comment: initial note | priority: low/medium/high/critical
- estimate: hours (float) | order: unique position (1,2,3,4) | parallel: bool (can run concurrently with adjacent parallel tasks) | tags: ["tag1", "tag2"] (max 10)
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.
- today First seen · 508 lines · 19 tokens per session scan A d5119556f300
commit-master is an agent published in the GitHub repository Xsaven/vector-memory-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 6,362 once invoked, about $0.0001 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-09-01.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.