agentmods.dev

searchpo-main-agent

searchpo-main-agent is an agent for Claude Code from SunflowersLwtech/sunkit. It costs 54 tokens per session (1,342 once invoked), scanned A, original, Apache-2.0.

A team lead for Searchpo agent runs, where Searchpo is a system for researching and publishing topics. It coordinates incoming topics and links, assigns work, checks release requirements, and makes final publishing decisions.

In plain words
What is it for?
Use it when asking for Searchpo full flow or widesearch work, or when coordinating a Searchpo agent team.
Why use it?
It gives a multi-agent run one place to manage assignments, checks, and publishing decisions.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; mentions Codex.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 agent_harness/run_agent_loop.py --topic "topic" --mode provider --stop-after research_enrichment --delegation-mode spawned_subagents --delegation-agent .

Part of the searchpo plugin — 8 skills, 1 command, 3 agents, 1 plugin shipped together

not rated 13repo yesterday A scan 54 tokens original Apache-2.0

Good fit Use it when asking for Searchpo full flow or widesearch work, or when coordinating a Searchpo agent team.

Compare 6 agents from other repositories ↓
View source ↗ SunflowersLwtech/sunkit sunflowerslwtech.github.io
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/SunflowersLwtech/sunkit
agentmods
npx agentmods add agents/sunflowerslwtech/sunkit/searchpo-main-agent

Made for: Claude Code.

Or install searchpo, the plugin that ships this one along with the rest of its 8 skills, 1 command, 3 agents, 1 plugin.

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 searchpo-main-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/sunflowerslwtech/sunkit/searchpo-main-agent/github.svg)](https://agentmods.dev/agents/sunflowerslwtech/sunkit/searchpo-main-agent)
Your own site
<a href="https://agentmods.dev/agents/sunflowerslwtech/sunkit/searchpo-main-agent"><img src="https://agentmods.dev/badge/agents/sunflowerslwtech/sunkit/searchpo-main-agent/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 searchpo-main-agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/sunflowerslwtech/sunkit/searchpo-main-agent"><img src="https://agentmods.dev/badge/agents/sunflowerslwtech/sunkit/searchpo-main-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,342 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.00054 $0.01342
Opus 5.5 $0.00022 $0.00537
Sonnet 5.5 $0.00011 $0.00268
Haiku 4.5 $0.00005 $0.00134

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

Security

Grade A, and why

searchpo-main-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 2mo 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.

plugins/searchpo/.claude/agents/searchpo-main-agent.md · 81 lines

How it starts

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

Searchpo Main Agent

You are the Searchpo team lead.

Responsibilities

  • Own main_task_plan.json, runtime_contract.json, research_barrier.json, release_gate.json, release-gate interpretation, and the final publish/no-publish decision.
  • Require an operator-supplied topic or link for normal runs. The legacy source-registry candidate sweep is opt-in only with SEARCHPO_ENABLE_DAILY_RADAR=1.
  • In Codex, when subagent tools are available, use sequential delegation: spawn or assign searchpo-research-agent first, wait for the research barrier to pass, then spawn or assign searchpo-impl-agent. Do not run them in parallel, and do not treat task owner labels as proof of real delegation.
  • Use python3 scripts/agent_capabilities.py --profile all --format text to inspect available provider/API/MCP capabilities without exposing .env values when planning work.
  • Assign widesearch and enriched cross-check to searchpo-research-agent before copy generation, with AnySearch source discovery/extraction first and DeepWiki only as supporting repo context.
  • Assign script execution, provider calls, rendering, audit, and upload/check tasks to searchpo-impl-agent only after research_barrier.json.status == "pass".
  • Verify implementation outputs by reading concrete artifacts under runtime/artifacts/YYYY-MM-DD/<run_id>/.
  • Treat release_gate.json, run_final.json, and artifact_manifest.json as final release truth in provider/live runs.
  • Keep live publishing behind an explicit current-run user request.
  • Record delegation truth in agent_run.json.delegation; spawned_subagents requires a host subagent/thread proof string, while single_harness and manual_fallback must not be reported as real agent-team execution.

Delegation Contract

Delegate these tasks to searchpo-research-agent:

  • Primary source fetch verification and AnySearch supplemental research.
  • GitHub API and README evidence for GitHub repo subjects.
  • DeepWiki MCP repo-context collection for GitHub repo subjects when available, after AnySearch-first evidence planning has started.
  • source_map.json, fact_bank.json, topic_brief.json, compatibility research_brief.json, anysearch_research.json, enriched evidence_bundle.json, and enriched cross_check_review.json.
  • Strong research gate enforcement: primary evidence plus at least two independent supplemental extracted sources.

Read the full file on GitHub · 81 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. 2mo ago First seen · 81 lines · 54 tokens per session scan A a003d045c022

Subscribe to this mod's changes

searchpo-main-agent is an agent published in the GitHub repository SunflowersLwtech/sunkit (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 1,342 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-08-30.

Claude CodeFrontendGit and workflowResearchcognitive-toolsdesign-systemprompt-engineeringtacit-knowledge
Related

Other agents, from other repositories

Gitmoji Setup

Sets up gitmoji (https://gitmoji.dev) commit tooling in a repository — audits the existing hook manager and commit convention, then installs the right option without clobbering existing hooks. Defaults to a non-interactive prepare-commit-msg hook that prefills a suggested emoji from the branch name and staged files…

github/awesome-copilot · 86 tokens

SE: DevOps/CI

DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable.

github/awesome-copilot · 29 tokens

GitHub Actions Node Runtime Upgrade

Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.

github/awesome-copilot · 45 tokens

Universal PR Comment Addresser

Your job is to address comments on your pull request.

github/awesome-copilot · 9 tokens

octopus-release-notes-with-mcp

Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.

github/awesome-copilot · 35 tokens

launchdarkly-flag-cleanup

A specialized GitHub Copilot agent that uses the LaunchDarkly MCP server to safely automate feature flag cleanup workflows. This agent determines removal readiness, identifies the correct forward value, and creates PRs that preserve production behavior while removing obsolete flags and updating stale defaults.

github/awesome-copilot · 60 tokens