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 jqaisystems/jqai-ai-skills --skill client-workspace-scaffoldergit clone --depth 1 https://github.com/jqaisystems/jqai-ai-skillsWrote 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/jqaisystems/jqai-ai-skills/client-workspace-scaffolder)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/client-workspace-scaffolder"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/client-workspace-scaffolder/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/jqaisystems/jqai-ai-skills/client-workspace-scaffolder"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/client-workspace-scaffolder.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.00067 | $0.00583 |
| Opus 5.5 | $0.00027 | $0.00233 |
| Sonnet 5.5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
client-workspace-scaffolder 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Workspace Scaffolder
Every client engagement starts with the same folder dance. This skill does it once, correctly, from a structure you define one time and reuse forever.
Step 0: Load the workspace template (once)
Look for a client-workspace.template.md file in the project root. If it does not exist, ask the user how they structure a client project, then offer to save the answers. The template defines:
CLIENTS_ROOT The parent folder where client folders live
FOLDERS The subfolders every client gets, e.g. Assets, Context, Strategy, Website
BRIEF_TEMPLATE The markdown skeleton for the brief file (status, scope checklist, references, billing section)
EXTRA_FILES Other starter files, e.g. Feedback.md with a feedback-round table
A sensible default when the user has no opinion yet:
CLIENTS_ROOT: ./Clients
FOLDERS: 01_Assets, 02_Context, Strategy
BRIEF_TEMPLATE: title, Status (Active/Completed/On hold), Started date,
Brief paragraph, Scope checklist, References, Files note, Billing section
EXTRA_FILES: Feedback.md with a Date/Round/Notes table
Step 1: Collect the essentials
From the user's message: client name (required) and project scope. Anything else they volunteer (industry, contact, deadline) goes into the brief. Ask at most one short round of questions.
Step 2: Check for collisions
List CLIENTS_ROOT first. If a folder with the same or a very similar name exists, stop and ask whether to use it or create a variant. Never overwrite an existing client folder or brief.
Step 3: Scaffold
Create the folder tree from FOLDERS, write the brief from BRIEF_TEMPLATE with everything known filled in (status Active, started today, scope boxes ticked), and create EXTRA_FILES. Leave unknowns as visible placeholders rather than fabricated values. Empty folders are correct; do not create filler files inside them.
Step 4: Report
Show the created tree and the brief contents. Mention the natural next step if the brief has gaps (a discovery conversation or intake questionnaire).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 67 tokens per session scan A 24532fa4f8c5
client-workspace-scaffolder is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 67 tokens to every session and 583 once invoked, about $0.0003 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-31.
Other skills, from other repositories
ledger-tasks-yylo
Retrieve any YYLO Ledger Record by ID, discover PDRs and artifacts, and manage tasks and dependencies. Use for unknown record types, universal get/search, task operations, and source-of-truth boundaries.
grill-me
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.
wiki-yylo
Use YYLO Ledger wiki Records as durable project knowledge. Search before creating, classify information correctly, and make revision-safe Markdown updates without editing Ledger storage directly.
plan-ledger-tasks-yylo
Create a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…