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.
git 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/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/agents/wshobson/agents/conductor-validator"><img src="https://agentmods.dev/badge/agents/wshobson/agents/conductor-validator.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.00034 | $0.01588 |
| Opus 5.5 | $0.00014 | $0.00635 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 246 lines · 34 tokens per session scan A f7957d977522
conductor-validator is an agent published in the GitHub repository wshobson/agents (41,474 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,588 once invoked, about $0.0001 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-03.
Other agents, from other repositories
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
project-manager
Project Manager. Coordinates sprints, tracks progress, removes blockers, ensures delivery.
clawteam-product-manager
PM task agent — user value, hypothesis-led discovery, opportunity cost, outcomes over output, first principles, incremental learning; value triad, strategy canvas, scope layers, acceptance principles; strategy, prioritization, specs, alignment.
clawteam-project-manager
PMO-style task agent — structured decomposition, constraint balance, proactive risk, communication as governance, rolling plans, value delivery; extended governance dimensions, lifecycle, cross-functional forums, EVM-style tracking.
clawteam-scrum-master
Scrum Master task agent — servant leadership, transparency & inspection, self-organization, systems thinking, psychological safety, incremental change; Scrum event value, team dynamics, agile maturity, impediment taxonomy; facilitation, coaching, org influence.
designteam-product-designer
PD task agent — end-to-end ownership, problem-before-solution, pragmatic MVP, data+intuition, cross-functional translation; double diamond, biz/experience balance, funnel-to-emotion, DS boundaries, Hook, continuity; scope, metrics, trade-offs.