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/commands/wshobson/agents/implement)<a href="https://agentmods.dev/commands/wshobson/agents/implement"><img src="https://agentmods.dev/badge/commands/wshobson/agents/implement/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/commands/wshobson/agents/implement"><img src="https://agentmods.dev/badge/commands/wshobson/agents/implement.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.00012 | $0.02097 |
| Opus 5.5 | $0.00005 | $0.00839 |
| Sonnet 5.5 | $0.00002 | $0.00419 |
| Haiku 4.5 | $0.00001 | $0.00210 |
Grade A, and why
implement 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Track
Execute tasks from a track's implementation plan, following the workflow rules defined in conductor/workflow.md.
Pre-flight Checks
-
Verify Conductor is initialized:
- Check
conductor/product.mdexists - Check
conductor/workflow.mdexists - Check
conductor/tracks.mdexists - If missing: Display error and suggest running
/conductor:setupfirst
- Check
-
Load workflow configuration:
- Read
conductor/workflow.md - Parse TDD strictness level
- Parse commit strategy
- Parse verification checkpoint rules
- Read
Track Selection
If argument provided:
- Validate track exists:
conductor/tracks/{argument}/plan.md - If not found: Search for partial matches, suggest corrections
If no argument:
-
Read
conductor/tracks.md -
Parse for incomplete tracks (status
[ ]or[~]) -
Display selection menu:
Select a track to implement: In Progress: 1. [~] auth_20250115 - User Authentication (Phase 2, Task 3) Pending: 2. [ ] nav-fix_20250114 - Navigation Bug Fix 3. [ ] dashboard_20250113 - Dashboard Feature Enter number or track ID:
Context Loading
Load all relevant context for implementation:
-
Track documents:
conductor/tracks/{trackId}/spec.md- Requirementsconductor/tracks/{trackId}/plan.md- Task listconductor/tracks/{trackId}/metadata.json- Progress state
-
Project context:
conductor/product.md- Product understandingconductor/tech-stack.md- Technical constraintsconductor/workflow.md- Process rules
-
Code style (if exists):
conductor/code_styleguides/{language}.md
Track Status Update
Update track to in-progress:
-
In
conductor/tracks.md:- Change
[ ]to[~]for this track
- Change
-
In
conductor/tracks/{trackId}/metadata.json:- Set
status: "in_progress" - Update
updatedtimestamp
- Set
Task Execution Loop
For each incomplete task in plan.md (marked with [ ]):
1. Task Identification
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 · 370 lines · 12 tokens per session scan A 8809377c6613
implement is a command published in the GitHub repository wshobson/agents (41,158 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 2,097 once invoked, about $0.0000 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 commands, from other repositories
rules
A command for managing coding rules stored in CLAUDE.md, AGENTS.md, and optional project RULES.md files. It can select built-in rules, add personal rules, change settings such as architecture or coverage, and control whether test-driven development (TDD) is required.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
test-management
Organize, classify, and trace Katalon True Platform/TestOps test assets. Use when you need to structure test cases into folders and suites, move or reorganize cases, search and find existing assets at scale, link or unlink requirements to test cases, or produce a requirement-to-test traceability report (which…
implement-approved-slice
Implement only the approved slice with minimal changes, then persist execution evidence in slice notes and TASKSTATE.md. The official execution path. Opt-in test-first mode via --tdd. Use when the plan and slice are approved, ambiguity is resolved and files in scope are known. Do not use during discovery or planning…
dev-tdd
Implements a feature by following the TDD (Test-Driven Development) cycle.
work-flow-bugfix
Complete workflow to fix a bug, from diagnosis to deployment.