Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. 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/TheSmokeDev/taskchad-os/master/.claude/commands/core_piv_loop/prime-workflows.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/prime-workflows)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/prime-workflows"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/prime-workflows.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.00025 | $0.00887 |
| Opus 5 | $0.00013 | $0.00443 |
| Sonnet 5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
prime-workflows 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prime: Archon Workflows Slice
Objective
Build understanding of the Archon workflow engine layer — how this project uses YAML DAG workflows, command files, worktree isolation, and the PIV loop (Plan-Implement-Validate) for coding tasks. Archon is the "hands" (deterministic multi-step coding) while The Homie is the "brain" (runtime, memory, reasoning).
Key Files to Read
Project config
@.archon/config.yaml
Active workflows (read all YAML files)
@.archon/workflows/archon-vault-a-grade.yaml @.archon/workflows/best-of-both-team-orchestration.yaml @.archon/workflows/archon-evolve-belief.yaml
PIV command suite (the core dev loop)
@.claude/commands/core_piv_loop/prime.md @.claude/commands/core_piv_loop/plan-feature.md @.claude/commands/core_piv_loop/execute.md
Validation + review commands
@.claude/commands/validation/validate.md @.claude/commands/validation/code-review.md @.claude/commands/commit.md
Bug fix commands
@.claude/commands/github_bug_fix/rca.md @.claude/commands/github_bug_fix/implement-fix.md
CLAUDE.md Archon section (search for "## Archon")
Read the Archon section of CLAUDE.md for workflow triggers, Ralph state pattern, Archon vs Convoy/Mailbox distinction.
Workflow YAML Structure
Workflows are YAML DAGs in .archon/workflows/. Structure:
name: workflow-name
description: When to use + what it does
provider: claude | codex
interactive: true | false
nodes:
- id: node-name
prompt: "..." # AI prompt
bash: "..." # Or shell command
depends_on: [other] # DAG edges
ai:
model: sonnet | opus
provider: codex # Cross-provider for anti-bias
denied_tools: [Write] # Read-only safety
Command File Structure
Commands are markdown in .archon/commands/ with YAML frontmatter. They're prompts callable from workflows or directly via archon workflow run.
Slice Boundaries
- Owns: workflow YAML definitions, command files, project config, PIV loop commands, validation commands, commit conventions
- Does NOT own: Archon binary (compiled Go at
~/.archon/bin/archon.exe— not editable), runtime memory pipelines, convoy/mailbox orchestration (that's the framework, not Archon) - Key distinction: Archon = developer coding workflows (feature dev, PR review). Convoy/Mailbox = runtime agent task coordination. Different systems, different state stores.
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.
- 8d ago First seen · 91 lines · 25 tokens per session scan A 560e43957a1b
prime-workflows is a command published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 887 once invoked, about $0.0001 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 commands, from other repositories
instinct-import
Import a portable YAML instinct pack with confidence-gated merge (Instinct Engine).
spawn
Spawn a worker agent session in a registered project. The session runs the chosen agent in a fresh git worktree. Register the project first with ao project add.
cierre
A sales call just ended: turn its transcript into the full follow-up (CRM, tasks, email draft, reminder, coaching).
patterns
Scan recent sessions for recurring patterns and turn them into captures (rules, concept notes, writing seeds).
second-brain-mapping
Map your vault: extract structured metadata from every typed file, surface cross-doc insights, optionally build a knowledge graph.
evolve
Cluster hardened instincts into a proposed Command / Skill / Agent (Instinct Engine).