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.
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/rules/ulises-jeremias/agent-toolkit/client-workflow-bootstrap)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/client-workflow-bootstrap"><img src="https://agentmods.dev/badge/rules/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.
<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/client-workflow-bootstrap"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/client-workflow-bootstrap.svg" alt="Reviewed on agentmods" width="80" 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.01353 | $0.01353 |
| Opus 5.5 | $0.00541 | $0.00541 |
| Sonnet 5.5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00135 | $0.00135 |
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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: client-workflow-bootstrap description: "Meta-generator / orchestrator — onboarding interview that meta-generates -workflow + -dev-companion skills and opens a draft PR. Use when onboarding a new client project or updating an existing delivery workflow skill pair; not a daily delivery persona." tools: Read, Grep, Glob, Bash, Write, Edit kind: orchestrator collaborates_with:
- assistant
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 orplanner's breakdown. Benefits from orchestrator framing andWrite/Editpermissions not shared broadly. Decision: KEEP AS ORCHESTRATOR (meta-generator; not holistic daily, not specialist review). Seedocs/AGENT_TAXONOMY.md§2 tiering andcapabilities/skills/registry.yamlholistic_owner: assistant+delivery/workflow-client-bootstrapalready orchestrator-tier.
When to use vs holistic
- Use this orchestrator for new/updated client delivery context →
~/.ai-workspacepacks/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→reviewerviadelivery/workflow-generic-project.
Caller / skills / handoff
- Caller (tier: orchestrator): User/workspace-init directly or
assistantwhen 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;
assistantresumes normal routing thereafter. Never required for day-to-day delivery.
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.
- 1mo ago First seen · 105 lines · 1,353 tokens per session scan A 11cddebba99d
client-workflow-bootstrap is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 1,353 tokens to every session, about $0.0054 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.
Other cursor rules, from other repositories
agent-workflow-orchestration
Mandatory PM-orchestrated subagent workflow — main agent is manager, no separate PM subagent.
collaboration-guidelines
General collaboration guidelines and project philosophy for team development.
task-tracking
Enforces active task management during coding sessions.
task-tracking
Adaptive task status tracking protocol (Single Source of Truth).
archive-examples
CRITICAL: Contains mandatory examples for correct archive formatting. DO NOT archive tasks without consulting this documentation first.
workflow-examples
CRITICAL: Contains mandatory examples for correct workflow implementation. DO NOT assume workflow patterns without consulting this documentation first.