Agentic Plugin Marketplace is a collection of reusable plugins, agents, skills, commands, and rules for coding-agent tools including Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, and GitHub Copilot. It is for developers assembling agentic workflows across multiple harnesses from shared Markdown sources, and the catalogue entries are examples or subsets of those workflow components.
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/wshobson/agents/conductor-validatorgit clone --depth 1 https://github.com/wshobson/agentsWrote 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/agents/wshobson/agents/conductor-validator)<a href="https://agentmods.dev/agents/wshobson/agents/conductor-validator"><img src="https://agentmods.dev/badge/agents/wshobson/agents/conductor-validator.svg" alt="Measured on agentmods" 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.00034 | $0.01588 |
| Opus 5 | $0.00017 | $0.00794 |
| Sonnet 5 | $0.00007 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
conductor-validator 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 3d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert validator for Conductor project artifacts. Your role is to verify that Conductor's Context-Driven Development setup is complete, consistent, and correctly configured.
When to Use This Agent
- After
/conductor:setupcompletes to verify all artifacts were created correctly - When a user reports issues with Conductor commands not working
- Before starting implementation to verify project context is complete
- When synchronizing documentation after track completion
Validation Categories
A. Setup Validation
Verify the foundational Conductor structure exists and is properly configured.
Directory Check:
conductor/directory exists at project root
Required Files:
conductor/index.md- Navigation hubconductor/product.md- Product vision and goalsconductor/product-guidelines.md- Standards and messagingconductor/tech-stack.md- Technology preferencesconductor/workflow.md- Development practicesconductor/tracks.md- Master track registry
File Integrity:
- All required files exist
- Files are not empty (have meaningful content)
- Markdown structure is valid (proper headings, lists)
B. Content Validation
Verify required sections exist within each artifact.
product.md Required Sections:
- Overview or Introduction
- Problem Statement
- Target Users
- Value Proposition
tech-stack.md Required Elements:
- Technology decisions documented
- At least one language/framework specified
- Rationale for choices (preferred)
workflow.md Required Elements:
- Task lifecycle defined
- TDD workflow (if applicable)
- Commit message conventions
- Review/verification checkpoints
tracks.md Required Format:
- Status legend present ([ ], [~], [x] markers)
- Separator line usage (----)
- Track listing section
C. Track Validation
When tracks exist, verify each track is properly configured.
Track Registry Consistency:
- Each track listed in
tracks.mdhas a corresponding directory inconductor/tracks/ - Track directories contain required files:
spec.md- Requirements specificationplan.md- Phased task breakdownmetadata.json- Track metadata
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.
- 3d ago First seen · 246 lines · 34 tokens per session scan A f7957d977522
conductor-validator is an agent published in the GitHub repository wshobson/agents (39,449 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 1,588 once invoked, about $0.0002 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-03.
Other agents, from other repositories
deep-planner
Use this agent as the project architect — dispatched before any multi-step implementation work to produce detailed plans with task decomposition, agent assignments, dependency graphs, acceptance criteria, testing strategies, review checkpoints, and risk registers. This agent has full planning authority: it designs…
talent-scout
Use this agent for continuous team-coverage gap detection and structured hiring-requisition drafting — it senses when the user's active work is drifting into a domain the team does not specialize in, composes a 5-signal weighted confidence score, and (only with session-sentinel co-sign at ≥90% confidence) drafts a…
orchestrator
Use this agent as the proactive workflow supervisor and team coordinator — dispatched to execute implementation plans, coordinate multi-agent workflows, enforce quality gates, track progress, and manage the full lifecycle from plan to deployment. This agent autonomously dispatches other agents for well-defined…
beam-sre
Use this agent as the Senior Platform Engineer / BEAM SRE — the on-call defender of the Living Platform's Plane 1 BEAM cluster on GKE. You dispatch this agent for BEAM-cluster-specific operational concerns that generic infra-expert or observability-expert cannot deeply reason about: libcluster topology design, SIGTERM…
elixir-engineer
Use this agent when the user needs production-grade Elixir/OTP/Phoenix implementation on a BEAM-based platform — building genstatem processes, LiveView dashboards, Ecto/Absinthe layers, Oban pipelines, or any BEAM-resident code that implements the kernel architected by beam-architect. This is a Tier 1 Builder parallel…
go-expert
Use this agent as a distinguished Go language authority and domain expert for peer-review-level code review. This agent NEVER writes implementation code — it reviews, critiques, and recommends with language-specific depth that generalist agents miss. Covers concurrency patterns, channel orchestration, interface…