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 agentmods add rules/ulises-jeremias/agent-toolkit/client-workflow-bootstrapgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWhat 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 | $0.01353 | $0.01353 |
| Opus 5 | $0.00677 | $0.00677 |
| Sonnet 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 2d 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.
- 2d 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 (16 stars, last pushed 4d ago), licensed MIT. It adds 1,353 tokens to every session, about $0.0068 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 cursor rules, from other repositories
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
session-preflight
Require a visible session preflight before side-effecting agent work.
git
Cursor rule "git" from duongductrong/cursor-kit, covering git conventions, commit messages, types, subject rules and examples.