obsidian-hybrid-search: Skill for Claude Code

.ai/skills/subagent-driven-development/SKILL.md

subagent-driven-development is a skill for Claude Code, Codex from flowing-abyss/obsidian-hybrid-search. It costs 17 tokens per session (7,591 once invoked), scanned C, a copy of subagent-driven-development, MIT.

A way to carry out an implementation plan by assigning each task to a fresh helper agent, reviewing that task, and then reviewing the completed branch. Helper agents are separate coding assistants with limited, specifically prepared context.

In plain words
What is it for?
Use it when executing a plan made of independent coding tasks. It coordinates task assignment, per-task review, and a final review of the branch.
Why use it?
It keeps tasks focused and adds checks for both requirement compliance and code quality without making every helper carry the whole conversation history.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

This is flowing-abyss/obsidian-hybrid-search's own configuration. It tells Claude Code and Codex how to work on obsidian-hybrid-search itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything obsidian-hybrid-search configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is "Dispatch final code reviewer (../requesting-code-review/code-reviewer.md)" [shape=box];.

Reuse

Borrowing it

Nothing to install: this file belongs to flowing-abyss/obsidian-hybrid-search. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/flowing-abyss/obsidian-hybrid-search/master/.ai/skills/subagent-driven-development/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/flowing-abyss/obsidian-hybrid-search

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for subagent-driven-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/subagent-driven-development/github.svg)](https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/subagent-driven-development)
Your own site
<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/subagent-driven-development/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for subagent-driven-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/subagent-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,591 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.07591
Opus 5.5 $0.00007 $0.03036
Sonnet 5.5 $0.00003 $0.01518
Haiku 4.5 $0.00002 $0.00759

Measured today against content hash bd33a2ab58bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

subagent-driven-development scanned grade C with 1 finding 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.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/review-package.mjs, scripts/review-package.test.mjs, scripts/sdd-workspace.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

delete this plan's workspace (`rm -rf <workspace>`) , the git history is
Origin

This is a copy

91% identical to subagent-driven-development — 406 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.ai/skills/subagent-driven-development/SKILL.md · 575 lines

How it starts

The opening of the file, as written. The whole thing — 575 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Subagent-Driven Development

Execute plan by dispatching a fresh implementer subagent per task, a task review (spec compliance + code quality) after each, and a broad whole-branch review at the end.

Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history , you construct exactly what they need. This also preserves your own context for coordination work.

Core principle: Fresh subagent per task + task review (spec + quality) + broad final review = high quality, fast iteration

Narration: between tool calls, narrate at most one short line , the ledger and the tool results carry the record.

Continuous execution: Do not pause to check in with your human partner between tasks. Execute all tasks from the plan without stopping. The only reasons to stop are the four named below, or all tasks complete. "Should I continue?" prompts and progress summaries waste their time , they asked you to execute the plan, so execute it.

Rulings, not stalls. A running plan does not wait on a human. Conflicts, ambiguities, plan defects, a cap you would have asked to exceed , decide them. The spec is the binding authority, the plan is its argument, and your judgment settles what neither answers. Record every decision in the ledger as Ruling: <what you decided> , <why> , <what it costs if wrong>, and keep going. A wrong ruling costs rework your human partner can see and undo; a session parked on a question costs their whole day and buys nothing.

Four things stop you, and only these: an irreversible or destructive operation; a security-sensitive action; a side effect outside this worktree that norms say you ask about first (a merge, a push to a shared branch, a publish); and a plan so broken that every path forward is a guess. For those, stop and ask.

When to Use

digraph when_to_use {
    "Have implementation plan?" [shape=diamond];
    "Tasks mostly independent?" [shape=diamond];
    "Partner chose inline, or no subagent tool?" [shape=diamond];
    "subagent-driven-development" [shape=box];
    "executing-plans" [shape=box];
    "Manual execution or brainstorm first" [shape=box];

    "Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
    "Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
    "Tasks mostly independent?" -> "Partner chose inline, or no subagent tool?" [label="yes"];
    "Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
    "Partner chose inline, or no subagent tool?" -> "executing-plans" [label="yes"];
    "Partner chose inline, or no subagent tool?" -> "subagent-driven-development" [label="no"];
}

Read the full file on GitHub · 575 lines

Changes

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.

  1. today First seen · 575 lines · 17 tokens per session scan C bd33a2ab58bc

Subscribe to this mod's changes

subagent-driven-development is a skill published in the GitHub repository flowing-abyss/obsidian-hybrid-search (113 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 7,591 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 91% identical to subagent-driven-development, differing in 406 lines, and is treated as a copy.

Related

Other skills, from other repositories

codemark

Manage structural code bookmarks that survive refactoring. Use when the user says "remember this", "bookmark this", "save this location", "load my bookmarks", "what do I have bookmarked", "mark this code", "codemark", or when starting a new session and needing to reload context from a previous session. Also use…

DanielCardonaRojas/codemark · 97 tokens

qdrant-vector-search

High-performance vector similarity search engine for RAG and semantic search. Use when building production RAG systems requiring fast nearest neighbor search, hybrid search with filtering, or scalable vector storage with Rust-powered performance.

davila7/claude-code-templates · 46 tokens

notebrain-assistant

Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like…

nmdra/notebrain-cli · 129 tokens

palaia-memory

Check this person's shared memory before answering anything about their own work, and add to it when something is worth keeping. It holds their projects, decisions and reasons, house conventions (naming, commit messages, tests, releases, review and escalation), people and hard-won details, and every AI tool they use…

byte5ai/palaia · 127 tokens

palaia-messenger

Register this session with the shared directory so other AI sessions and this person's dashboard can see what you are doing, then use it to reach another live session directly instead of relaying everything through the person. Use it at the start of a task, before picking one up, when your work depends on or informs…

byte5ai/palaia · 82 tokens

palaia-capture

Save what this person tells you into their shared memory, which every AI tool they use can read. Use it the moment they state a decision and the reason for it, a convention, a correction, or a detail that was expensive to work out — including when they mention it in passing on the way to a different question. Save it…

byte5ai/palaia · 87 tokens