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 skills add jstoup111/ai-conductor --skill prgit clone --depth 1 https://github.com/jstoup111/ai-conductorWrote 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/skills/jstoup111/ai-conductor/pr)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/pr"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/pr/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/skills/jstoup111/ai-conductor/pr"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 185 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium MCP Rug Pull · line 133 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00038 | $0.02006 |
| Opus 5.5 | $0.00015 | $0.00802 |
| Sonnet 5.5 | $0.00008 | $0.00401 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
pr 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 23d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Creates high-quality pull requests by analyzing the actual changes, not parroting planning artifacts. The PR should tell a reviewer what changed, why, and how to verify it — nothing more.
Practices
1. Gather Context
Collect everything needed to understand the PR. Run these in parallel:
# Determine base branch (main or master)
git remote show origin | grep 'HEAD branch'
# Full commit log for this branch
git log --oneline <base>..HEAD
# Stat summary of all changes
git diff --stat <base>..HEAD
# Targeted hunks for the files whose behavior the PR must explain
git diff <base>..HEAD -- <path>
Do not print the whole branch diff when the stat shows a large change: a PR body needs the shape of the change, and a multi-thousand-line diff costs far more context than the prose it informs. Read the full diff only when it is small.
Also check for harness artifacts that provide motivation context:
.docs/specs/*.md— design docs (the "why").docs/stories/*.md— acceptance criteria.pipeline/conduct-state.json— feature name if available
2. Analyze Changes
Read the diff carefully and categorize what changed:
- New files — what do they introduce?
- Modified files — what behavior changed?
- Deleted files — what was removed and why?
- Migrations — any schema changes?
- Tests — what's covered?
- Config/infra — docker, CI, dependencies?
Group changes by logical area (e.g., "Notifications module", "Auth projection", "Alembic migrations"), not by file path.
3. Write the Title
Check for project conventions first:
Look for PR title format conventions in the project's CLAUDE.md under a
### PR Title Format heading (or similar). Projects may specify their preferred format
(conventional commits, ticket prefixes, etc.). If found, follow those conventions instead
of the defaults below.
Common project convention examples:
- Conventional Commits:
feat: add notification channel,fix(auth): resolve token expiry - Ticket prefix:
[PROJ-123] Add notification channel - Type/scope:
feat(notifications): add in-app channel
What ships with it
1 file beside SKILL.md 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.
- 23d ago Changed · +4 lines · -1 tokens per session 59e5b4424feb
- 1mo ago Changed · +1 lines 7f847291dbf3
- 1mo ago Changed · -67 lines 4dc8aba2f577
- 2mo ago First seen · 268 lines · 39 tokens per session scan A 8353bb86a17d
pr is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 2,006 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.