Borrowing it
Nothing to install: this file belongs to NguyenSiTrung/Conductor-Beads. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NguyenSiTrung/Conductor-Beads/main/.claude/skills/conductor/references/commands/validate.mdgit clone --depth 1 https://github.com/NguyenSiTrung/Conductor-BeadsWrote 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/nguyensitrung/conductor-beads/validate)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/validate"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/validate.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.00000 | $0.00671 |
| Opus 5 | $0.00000 | $0.00336 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
validate 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 4d 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.
This is a copy
92% identical to conductor-validate — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Validate
Validate the integrity of this Conductor project.
1. Core Files Check
Verify these files exist in conductor/:
product.mdtech-stack.mdworkflow.mdtracks.md
2. Tracks Consistency
For each track in tracks.md:
- Verify directory exists:
conductor/tracks/<track_id>/ - Verify files:
metadata.json,spec.md,plan.md - Validate metadata.json has: track_id, type, status, created_at
3. Orphan Detection
- List all directories in
conductor/tracks/ - Report any not referenced in
tracks.md
4. Status Consistency
- Compare status markers in
tracks.mdwithmetadata.jsonstatus field - Report mismatches
5. Plan Integrity
For each plan.md:
- Must have at least one phase and task
- Valid markers only:
[ ],[~],[x],[!] - Completed tracks should have all tasks completed
- Validate parallel execution annotations if present
5a. Parallel Execution Validation
For tracks with parallel execution annotations:
- Check
<!-- execution: parallel -->is after valid phase heading - Verify all tasks in parallel phases have
<!-- files: ... -->annotation - Detect file conflicts (same file in multiple tasks)
- Verify
<!-- depends: ... -->references valid task IDs - If
parallel_state.jsonexists, check for stale/orphan workers
6. Report
Present summary with:
- ✅ Valid items
- ⚠️ Warnings
- ❌ Errors
- Recommendations for fixes
7. Auto-Fix Option
Offer to fix auto-fixable issues:
- Missing metadata fields
- Status mismatches
- Orphan cleanup
8. BEADS VALIDATION
PROTOCOL: Include Beads consistency checks.
-
Check for Beads CLI:
- Run
which bd - If NOT found:
"⚠️ Beads CLI (
bd) is not installed. Beads provides persistent task memory across sessions." "A) Continue validation without Beads checks" "B) Stop - I'll install Beads first"- If A: Skip this section
- If B: HALT and wait for user
- Run
-
Verify Beads Integration:
- Task status sync between Beads and plan.md
- No orphan epics/tasks
- Epic links valid in metadata.json
- If any
bdcommand fails:"⚠️ Beads command failed: " "A) Continue validation without Beads checks" "B) Retry the failed command" "C) Stop - I'll fix the issue first"
- If A: Skip remaining Beads steps
- If B: Retry the command
- If C: HALT and wait for user
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.
- 4d ago First seen · 93 lines · 0 tokens per session scan A 50248f7f3e89
validate is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 671 tokens. A static security scan graded it A with 0 findings. It is 92% identical to conductor-validate, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.