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/britt/agent-skillsWrote 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/plugins/britt/agent-skills/supervising-conductor-workspaces)<a href="https://agentmods.dev/plugins/britt/agent-skills/supervising-conductor-workspaces"><img src="https://agentmods.dev/badge/plugins/britt/agent-skills/supervising-conductor-workspaces/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/plugins/britt/agent-skills/supervising-conductor-workspaces"><img src="https://agentmods.dev/badge/plugins/britt/agent-skills/supervising-conductor-workspaces.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
supervising-conductor-workspaces 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 yesterday.
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.
What it actually says
{
"name": "supervising-conductor-workspaces",
"description": "Dispatch one Conductor workspace per issue and supervise their PRs to merge: keep them current with the base branch, resolve conflicts, rerun transient CI failures, tell green PRs to merge, and archive each workspace once its PR lands",
"version": "1.0.0",
"author": {
"name": "Britt Crawford"
},
"source": "./skills/supervising-conductor-workspaces",
"category": "development",
"tags": [
"conductor",
"workspaces",
"pull-requests",
"ci",
"monitoring",
"orchestration",
"github"
]
}What it installs
The manifest is a name and a version. 1 skill, 1 agent travel with it, and installing the plugin installs all of them — 317 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside marketplace.json#supervising-conductor-workspaces in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 19 lines scan A c196c017a14c
supervising-conductor-workspaces is a plugin published in the GitHub repository britt/agent-skills (9 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-29.
Other plugins, from other repositories
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
tgc-skills
A shipping pipeline for Claude Code: orchestrate a locked plan or a list of fixes with fresh-context agents or Orca/herdr/cmux worker panes, polish and explain the diff, ship it to a plain-language PR, run an incremental agent review-fix loop until clean, and clean up after merge.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
gh-cli
GitHub CLI integration with focused skills for pull requests, stacked pull requests, issues, GitHub Actions, and viewing GitHub file URLs.
github
Drive PRs to merge-ready with gh: fix CI and review-bot feedback, plus bulk merge, close, and label.