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 robertbarclayy/conducty --skill conducty-shipgit clone --depth 1 https://github.com/robertbarclayy/conductyWrote 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/robertbarclayy/conducty/conducty-ship)<a href="https://agentmods.dev/skills/robertbarclayy/conducty/conducty-ship"><img src="https://agentmods.dev/badge/skills/robertbarclayy/conducty/conducty-ship/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/robertbarclayy/conducty/conducty-ship"><img src="https://agentmods.dev/badge/skills/robertbarclayy/conducty/conducty-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Anti-Refusal · line 37 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00108 | $0.01961 |
| Opus 5 | $0.00054 | $0.00981 |
| Sonnet 5 | $0.00022 | $0.00392 |
| Haiku 4.5 | $0.00011 | $0.00196 |
Grade A, and why
conducty-ship 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 9d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conducty Ship — The Pre-Merge Gate
[[conducty-checkpoint]] gates a parallelization group inside a plan. [[conducty-code-review]] gives a holistic human-style read of the branch. conducty-ship is the last gate before merge: it runs the actual mechanical checks every project must pass and produces a single ship-or-don't verdict.
[!important] Read [[conducty-obsidian]] first Output goes to the vault as
Ship Reports/Ship Report YYYY-MM-DD HHmm.md, linked from the plan note and the code-review note.
When to Use
- After [[conducty-code-review]] verdict is
passorneeds-fix(with fixes applied) - Before merging to main, opening a release PR, or deploying
- The user says "ship it", "ready to merge", "ship gate", "pre-merge check"
Skip when:
- The plan hasn't been reviewed yet — run [[conducty-code-review]] first
- The branch is not yet a candidate for merge (still mid-plan)
The Battery
Six gates. Every gate must pass for ship verdict to be green. A single failure in any gate produces verdict red. Yellow exists only for Code review: needs-fix with all fixes applied but not re-reviewed — flag it but treat operationally as red.
| # | Gate | What runs | Pass criterion |
|---|---|---|---|
| 1 | Code review | Read Code Reviews/Code Review YYYY-MM-DD HHmm.md from the vault |
Verdict pass, or needs-fix with all Important/Critical findings checked off |
| 2 | Lint / format | Project's lint command (npm run lint, cargo clippy, ruff, etc.) |
Exit 0, no warnings the project treats as errors |
| 3 | Type check | Project's typechecker (tsc --noEmit, mypy, cargo check) |
Exit 0, no errors |
| 4 | Test suite | Full test suite (npm test, cargo test, pytest, etc.) |
Exit 0, no failures, no skipped tests added in this branch |
| 5 | Secrets scan | git diff $(git merge-base HEAD main)..HEAD piped through a secret-pattern grep |
No matches against secret patterns (API keys, tokens, credentials) |
| 6 | Dependency vulnerabilities | npm audit, pip-audit, cargo audit, osv-scanner, etc. — whichever fits the project |
No new High/Critical vulns introduced by this branch's dependency changes |
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.
- 9d ago First seen · 156 lines · 108 tokens per session scan A 3a6b867d349b
conducty-ship is a skill published in the GitHub repository robertbarclayy/conducty (176 stars, last pushed 2mo ago), licensed MIT. It adds 108 tokens to every session and 1,961 once invoked, about $0.0005 per session on Opus 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-30.
Other skills, from other repositories
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.