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 skills add Mr-remon219/search-boost --skill search-boost-parallel-researchgit clone --depth 1 https://github.com/Mr-remon219/search-boostWrote 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/skills/mr-remon219/search-boost/search-boost-parallel-research)<a href="https://agentmods.dev/skills/mr-remon219/search-boost/search-boost-parallel-research"><img src="https://agentmods.dev/badge/skills/mr-remon219/search-boost/search-boost-parallel-research/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.
<a href="https://agentmods.dev/skills/mr-remon219/search-boost/search-boost-parallel-research"><img src="https://agentmods.dev/badge/skills/mr-remon219/search-boost/search-boost-parallel-research.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.01498 |
| Opus 5.5 | $0.00022 | $0.00599 |
| Sonnet 5 | $0.00011 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
search-boost-parallel-research 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel research
Antigravity: use MCP server search-boost from global or workspace mcp_config.json, rather than search_web/read_url_content for these workflows. Use authorized cloud tools, not web search, for live account state.
This is a workflow, not an additional MCP tool or an installed subagent definition. The parent runs it using the host's existing capabilities and permissions. No Pi installation or CLI is needed.
Host execution
Capability-gated Antigravity workflow: the presence of an Agent Manager UI does not establish that this conversation has a callable subagent API. Inspect actual registered tools and use only a native, authorized delegation mechanism with retrievable child results. Do not invent a spawn tool or assume UI-level agents can be controlled from a skill.
Children must have access to the active global/workspace search-boost MCP connection, not merely the parent's visible tool list. Pass actual tool names and the shared role instructions explicitly, keep returned IDs, and use available wait/stop controls. No shell-spawned Pi runtime or permission changes. If native delegation or child MCP access is absent, use the shared workflow's disclosed serial path; keep synthesis in the parent.
Shared workflow
Use direct search for one lookup. Use this workflow only for independent research angles and only when delegation is authorized by the user and host policy. Loading this text is not authorization to spawn agents, enable features, or change permissions.
- Define the question, scope, relevant version/date, sufficient evidence, and budget. Split only genuinely independent angles; usually 2–4 searchers suffice, within the host's concurrency limits. Keep research read-only.
- Give each searcher the question context, one bounded task, the shared searcher instructions (injected by the native runner, or copied below from the skill), the actual search/read tool names, and a stopping condition. Do not assume a child sees this skill or the parent's tools/context.
- Start one wave through the host's real delegation mechanism; preserve run IDs and track completion, failure, timeout, and cancellation separately. Wait through the host's supported notification/wait mechanism, not repeated polling. Cancel remaining children on user cancellation and release owned child resources when supported.
- Fast mode: one wave, then the parent synthesizes and stops. Complex mode: pass all reports and their statuses to a no-search summarizer (or do that reasoning in the parent). Default 1–2 waves, at most 3. Launch only material new gap tasks, within the original budget; stop earlier when evidence is sufficient.
- The parent checks important claims against supplied evidence, resolves conflicting versions/dates, and produces the final cited answer. A URL list or domain count is not proof of corroboration. Keep single-source claims and remaining uncertainty explicit. Disclose failed tasks, partial/truncated reports, and any serial fallback.
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 · 87 lines · 56 tokens per session scan A 56cf40a02827
search-boost-parallel-research is a skill published in the GitHub repository Mr-remon219/search-boost (10 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 1,498 once invoked, about $0.0002 per session on Opus 5.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-21.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
ponytail-lazy-senior-dev
Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni"…
tdd-explore-ideas
Systematic codebase exploration, architectural critique, and 5-step Idea Assessment with TDD hypothesis verification for Phase 0.