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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wshobson/agentsnpx agentmods add commands/wshobson/agents/manageWrote 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/manage)<a href="https://agentmods.dev/commands/wshobson/agents/manage"><img src="https://agentmods.dev/badge/commands/wshobson/agents/manage.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.00014 | $0.06102 |
| Opus 5 | $0.00007 | $0.03051 |
| Sonnet 5 | $0.00003 | $0.01220 |
| Haiku 4.5 | $0.00001 | $0.00610 |
Grade C, and why
manage scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf conductor/tracks/{track-id} How it starts
The opening of the file, as written. The whole thing — 1,127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Track Manager
Manage the complete track lifecycle including archiving, restoring, deleting, renaming, and cleaning up orphaned artifacts.
Pre-flight Checks
-
Verify Conductor is initialized:
- Check
conductor/product.mdexists - Check
conductor/tracks.mdexists - Check
conductor/tracks/directory exists - If missing: Display error and suggest running
/conductor:setupfirst
- Check
-
Ensure archive directory exists (for archive/restore operations):
- Check if
conductor/tracks/_archive/exists - Create if needed when performing archive operation
- Check if
Mode Detection
Parse arguments to determine operation mode:
| Argument | Mode | Description |
|---|---|---|
--list [filter] |
List | Show all tracks (optional: active, completed, archived) |
--archive <id> |
Archive | Move completed track to archive |
--archive --bulk |
Bulk Archive | Multi-select completed tracks |
--restore <id> |
Restore | Restore archived track to active |
--delete <id> |
Delete | Permanently remove a track |
--rename <old> <new> |
Rename | Change track ID |
--cleanup |
Cleanup | Detect and fix orphaned artifacts |
| (none) | Interactive | Menu-driven operation selection |
Interactive Mode (no argument)
When invoked without arguments, display the main menu:
1. Gather Quick Stats
Read conductor/tracks.md and scan directories:
- Count active tracks (status
[ ]or[~]) - Count completed tracks (status
[x], not archived) - Count archived tracks (in
_archive/directory)
2. Display Main Menu
================================================================================
TRACK MANAGER
================================================================================
What would you like to do?
1. List all tracks
2. Archive a completed track
3. Restore an archived track
4. Delete a track permanently
5. Rename a track
6. Cleanup orphaned artifacts
7. Exit
Quick stats:
- {N} active tracks
- {M} completed (ready to archive)
- {P} archived
Select option:
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 · 1,127 lines · 14 tokens per session scan C 3aa0fcbbd61f
manage is a command published in the GitHub repository wshobson/agents (39,449 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 6,102 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
update-docs
Scan for recently modified files and update corresponding documentation.
handoff
Create a handoff document for seamless session continuity.
roadmap-track.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
vision-init.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
vision-new-product.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
github-menu-issues-list.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.