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 tikalk/adlc-team-skills --skill workspacegit clone --depth 1 https://github.com/tikalk/adlc-team-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/tikalk/adlc-team-skills/workspace)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/workspace"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/workspace/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/tikalk/adlc-team-skills/workspace"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/workspace.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 Excessive Agency · line 306 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00054 | $0.03478 |
| Opus 5 | $0.00027 | $0.01739 |
| Sonnet 5 | $0.00011 | $0.00696 |
| Haiku 4.5 | $0.00005 | $0.00348 |
Grade A, and why
workspace 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 9d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workspace
Overview
A multi-repo workspace coordinator for shared team context. The parent
repository holds shared decisions (PDRs, ADRs, CDRs) under .adlc/,
created by product-specify, architect-specify, and levelup-specify.
Child implementation repositories are discovered at depth 1 and optionally
linked as Git submodules so the entire workspace can be cloned with
git clone --recursive.
No workspace.yml, no registry file. Pure convention:
- Parent repo = current working directory (must be a Git repo)
- Child repos = depth-1 subdirectories containing
.git/ - Shared context =
.adlc/in parent root
When to Use
- First-time setup (
--init): Create.adlc/directory structure, configure.gitignoreconventions, and optionally link child repos. - After
product-specifyorarchitect-specifyhas created shared PDRs/ADRs in the parent repo and you have multiple implementation repos alongside. - When you've cloned new child repos into the workspace and want to register them as submodules (
--link) or ignore them (--ignore-only). - To audit workspace health: dirty working trees, unpushed commits, SHA drift between parent submodule reference and child HEAD.
- To verify child repos can see the parent
.adlc/shared context.
When NOT to Use --init
- Workspace already initialized: Use
/workspace --statusto audit instead. - Only auditing child repo state: Use
/workspace(read-only discovery + status). - Linking additional child repos after init: Use
/workspace --linkdirectly.
User Input
$ARGUMENTS
Commands
| Command | Purpose |
|---|---|
/workspace --init |
Initialize: create .adlc/ structure, configure .gitignore, discover child repos |
/workspace |
Discover child repos, show summary status (read-only) |
/workspace --link |
Convert child repos to Git submodules (requires clean parent tree) |
/workspace --status |
Detailed audit: branch, dirty, unpushed, SHA drift, .adlc presence |
/workspace --ignore-only |
Add child repos to .gitignore instead of creating submodules |
/workspace --init --link |
Initialize + link child repos in one step |
/workspace --init --ignore-only |
Initialize + add child repos to .gitignore |
/workspace --dry-run |
Preview changes without executing (combine with --init, --link, --ignore-only) |
/workspace --force |
Convert repos already tracked by parent index (requires clean tree) |
What ships with it
3 files 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.
- 9d ago First seen · 345 lines · 54 tokens per session scan A bbea59316fea
workspace is a skill published in the GitHub repository tikalk/adlc-team-skills (133 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 3,478 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-08-30.
Other skills, from other repositories
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…
status
Show a comprehensive project status dashboard: task queue, blocked items, session state, verification, and git status.
creating-issues-and-pull-requests
Use when creating GitHub pull requests or issues with template compliance. Triggers: 'create a PR', 'open a pull request', 'file an issue', 'create issue'. Also invoked by finishing-a-development-branch. NOT for: deciding whether to merge or PR (use finishing-a-development-branch).
plastic-project-creating
Create a new project from an implementation intent. Sets up project directory, git init, AGENTS.md with founding intent decisions, plastic-install --local, tactical mirror, projects.yml registration, and framework scaffolding. Use when an implementation intent spawns a project, or manually by user.
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.
jira-issue-deliver
Autonomously deliver one Jira issue from intake to a ready GitHub pull request. Use only when the user authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback.