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 skills/xpcoffee/nvim-markdown-notes-memgraph/orchestratenpx skills add xpcoffee/nvim-markdown-notes-memgraph --skill orchestrategit clone --depth 1 https://github.com/xpcoffee/nvim-markdown-notes-memgraphWhat 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.00018 | $0.00524 |
| Opus 5 | $0.00009 | $0.00262 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
orchestrate 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 yesterday.
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.
What it actually says
Orchestrate PRD Tasks
You coordinate the execution of PRD tasks by spawning coder subagents.
Steps
-
Read prd.json and identify all tasks with
"status": "pending". -
Parse the argument to determine scope:
- No argument or
next: run the next pending task (lowest ID) phase N(e.g.phase 2): run all pending tasks in phase N, sequentially- A task ID (e.g.
2.1): run that specific task N tasks(e.g.3 tasks): run the next N pending tasks sequentially
- No argument or
-
For each task in scope, spawn a
codersubagent via the Task tool:- Set
subagent_typeto"coder" - Include in the prompt:
- The task ID, description, phase, category
- The full steps array
- Instruction to read CLAUDE.md and ARCHITECTURE.md first
- Example:
Task(coder): Implement PRD task 1.2 Prompt: | Implement task 1.2 from prd.json. ID: 1.2 Phase: 1 Category: setup Description: Set up src/nvim_markdown_notes_memgraph/ package structure Steps: 1. Create src/nvim_markdown_notes_memgraph/ directory 2. Create __init__.py with version 3. Verify package imports work Read CLAUDE.md and ARCHITECTURE.md first for project context and workflow.
- Set
-
After each subagent completes, read
prd.jsonto verify the task status was updated. -
Report results:
- List which tasks completed successfully
- List which tasks failed (if any)
- Show count of remaining pending tasks
Notes
- Run tasks sequentially, not in parallel
- Tasks in phase 7 modify files in
/home/rick/code/personal/nvim-markdown-notes(outside this repo) - If a task fails, report it and continue to the next task in scope
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.
- yesterday First seen · 58 lines · 18 tokens per session scan A 6a3b4857380e
orchestrate is a skill published in the GitHub repository xpcoffee/nvim-markdown-notes-memgraph (0 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 524 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.