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 skills add ulises-jeremias/agent-toolkit --skill workflow-client-bootstrapgit 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/skills/ulises-jeremias/agent-toolkit/workflow-client-bootstrap)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/workflow-client-bootstrap"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/workflow-client-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/skills/ulises-jeremias/agent-toolkit/workflow-client-bootstrap"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/workflow-client-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 11 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00050 | $0.01364 |
| Opus 5 | $0.00025 | $0.00682 |
| Sonnet 5 | $0.00010 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
workflow-client-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 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Client Bootstrap
Use this skill to create or update a client-specific delivery context for any project.
It runs a structured interview and stores the result inside the user’s workspace
(~/.ai-workspace, ~/.ai-workspace, or a workspace-like directory) as packs + knowledge
(not new skills).
All generated files, PR text, and Jira/ClickUp comments must be in English.
When to use
- Onboarding a new client project that needs its own delivery workflow (beyond
workflow-generic-project) - Updating an existing workflow with new lifecycle states, repos, or guardrails
- Documenting a client's ticket lifecycle so future agent sessions can use correct status transitions
Do not use when
- The project already has an up-to-date workflow skill and only a ticket or code change is needed
- The work fits entirely within
workflow-generic-projectwithout client-specific gates
Interview process
Read questions.yaml (co-located with this skill) before starting. It defines multiple question groups.
| Group | Topics |
|---|---|
| Identity | Client name, slug, ticket system, docs platform, repo host |
| Workflow | Custom ticket statuses, done criteria, base branch, staging/QA gates |
| Stack | Repository list with roles, AGENTS.md presence, validation tools |
| Conventions | Branch naming, PR style, guardrails, Slack channel |
Workspace root selection (mandatory)
Before asking client questions, resolve the workspace root directory:
- Look for workspace-like directories (in order):
~/.ai-workspace~/.ai-workspace- the current working directory if it looks like a workspace (has
packs/andknowledge/) - other close matches (e.g.
~/*workspace*) that contain bothpacks/andknowledge/
- If exactly one plausible workspace is found, select it and print:
Using workspace: <path>. - If multiple are found, present a numbered list and ask which one to use.
- If none are found, explain the expected structure and ask the user for the path to use.
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 · 149 lines · 50 tokens per session scan A b6d6a3e237c9
workflow-client-bootstrap is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,364 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
iblai-api-agent-support
Manage an ibl.ai agent's human-support tickets via the platform API — list and filter the tickets users raised with an agent (by agent, requester, status, session), read a ticket's conversation thread, reply as the support team, change ticket status, and close or delete tickets. Use when triaging or responding to…
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…
breaking-down-work
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a deliverable, or build a work breakdown…
capturing-meeting-actions
Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this".
mapping-dependencies
Maps task dependencies in an Astravue project, finds the critical path and blocked work, and detects circular dependencies before any rescheduling. Use when the user asks about dependencies, blockers, what's blocking what, the critical path, or wants to understand or fix the sequencing of a project.
triaging-overdue-work
Reviews overdue and at-risk tasks in Astravue, assesses why each is slipping, and proposes reschedule, reassign, deprioritize, or close actions before applying them. Use when the user asks what's overdue, behind schedule, slipping, or at risk, wants to catch up on a project, or clean up late work.