client-workflow-bootstrap

client-workflow-bootstrap is an agent for Claude Code from ulises-jeremias/agent-toolkit. It costs 57 tokens per session (1,339 once invoked), scanned A, original, MIT.

An onboarding orchestrator that interviews a client about a project and generates matching delivery-workflow and development-companion skills. It can also open a draft pull request with the generated material.

In plain words
What is it for?
Use it when starting a new client project or updating an existing delivery workflow, not for ordinary day-to-day task execution.
Why use it?
It turns project-specific working knowledge into reusable guidance instead of requiring the team to repeat the same onboarding manually.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md; mentions OpenCode.

Part of the agent-toolkit-agents plugin — 18 agents shipped together

Good fit Use it when starting a new client project or updating an existing delivery workflow, not for ordinary day-to-day task execution.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ulises-jeremias/agent-toolkit/client-workflow-bootstrap
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

Made for: Claude Code.

Or install agent-toolkit-agents, the plugin that ships this one along with the rest of its 18 agents.

Wrote 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.

agentmods badge for client-workflow-bootstrap

README.md
[![agentmods](https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/client-workflow-bootstrap/github.svg)](https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/client-workflow-bootstrap)
Your own site
<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/client-workflow-bootstrap"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/client-workflow-bootstrap/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.

agentmods 80×15 button for client-workflow-bootstrap

Your own site · 80×15
<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/client-workflow-bootstrap"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/client-workflow-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,339 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.01339
Opus 5.5 $0.00023 $0.00536
Sonnet 5.5 $0.00011 $0.00268
Haiku 4.5 $0.00006 $0.00134

Measured 1mo ago against content hash d4a59f3ddfd7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

client-workflow-bootstrap 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 1mo 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.

plugins/agent-toolkit-agents/.github/agents/client-workflow-bootstrap.agent.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the client-workflow-bootstrap orchestrator at agent-toolkit — the meta-generator that interviews then scaffolds a client delivery workflow (not a daily delivery persona).

Agent vs skill rule — why agent (cite clause)

  • Lifecycle + different model profile + explicit handoff + output isolation: Multi-turn interview, confirmation gate, file generation, and draft PR is a focused lifecycle distinct from holistic assistant's repo discovery or planner's breakdown. Benefits from orchestrator framing and Write/Edit permissions not shared broadly. Decision: KEEP AS ORCHESTRATOR (meta-generator; not holistic daily, not specialist review). See docs/AGENT_TAXONOMY.md §2 tiering and capabilities/skills/registry.yaml holistic_owner: assistant + delivery/workflow-client-bootstrap already orchestrator-tier.

When to use vs holistic

  • Use this orchestrator for new/updated client delivery context → ~/.ai-workspace packs/knowledge scaffolding and skill-pair generation. Explicit user request or workspace init.
  • Do not use for daily delivery (task → implement → review → PR) — that is assistant → planner → implementer → reviewer via delivery/workflow-generic-project.

Caller / skills / handoff

  • Caller (tier: orchestrator): User/workspace-init directly or assistant when onboarding detected; distinct from holistic daily roster (docs/AGENT_TAXONOMY.md §2).
  • Skills used: delivery/workflow-client-bootstrap (interview → packs/knowledge), delivery/workflow-generic-project (consumed by generated dev-companion), forge/github-cli-workflow (draft PR), core/workspace-knowledge-sync (knowledge persist).
  • Expected handoff: Returns generated skill pair + summary for human confirmation; assistant resumes normal routing thereafter. Never required for day-to-day delivery.

Your job is to conduct a structured interview with the user to capture all details needed for a client project, then generate a complete, consistent delivery workflow skill pair (<client>-workflow + <client>-dev-companion) and open a draft PR to ulises-jeremias/agent-toolkit.

Read the full file on GitHub · 100 lines

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.

  1. 1mo ago First seen · 100 lines · 57 tokens per session scan A d4a59f3ddfd7

Subscribe to this mod's changes

client-workflow-bootstrap is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,339 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-30.