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 shadcn-labs/agentcn --skill workspacegit clone --depth 1 https://github.com/shadcn-labs/agentcnWrote 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/shadcn-labs/agentcn/workspace)<a href="https://agentmods.dev/skills/shadcn-labs/agentcn/workspace"><img src="https://agentmods.dev/badge/skills/shadcn-labs/agentcn/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/shadcn-labs/agentcn/workspace"><img src="https://agentmods.dev/badge/skills/shadcn-labs/agentcn/workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00118 |
| Opus 5.5 | $0.00009 | $0.00047 |
| Sonnet 5.5 | $0.00005 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
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 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.
What it actually says
Working in the Workspace
- Plan the task as a short ordered checklist.
- Inspect first: read files or
lsa directory before changing anything. - Make the smallest change that advances the task; re-check after each step.
- Keep every path inside the workspace.
- Prefer reversible, non-destructive commands. Explain risky ones before running.
- Finish by summarizing exactly what you created or changed.
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 · 14 lines · 23 tokens per session scan A e14da5b1b6b9
workspace is a skill published in the GitHub repository shadcn-labs/agentcn (494 stars, last pushed 16d ago), licensed MIT. It adds 23 tokens to every session and 118 once invoked, about $0.0001 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 skills, from other repositories
agent-readme
Write or deslopify a registry agent's README (registry/ /README.md). Use when authoring a new agent README, trimming an existing one, or cutting AI-generated README noise ("these READMEs are too long / generic / repetitive", "deslopify the readmes", "fix the README"). Not for agent/instructions.md, the runtime prompt.
revenue-pulse
Use when writing the weekly Stripe revenue & churn pulse — how to pull facts with the stripe and posthog-cli CLIs in the sandbox, then post to Slack.
author-atom-eve-agent
Use when authoring or contributing a NEW Atom Eve agent to the registry (not installing an existing one) - designing what it does, wiring its capability and connections, and writing the README, SETUP.md, and agent/ source. Triggers include "build a new Atom Eve agent", "contribute an agent", "add a new agent to the…
ppc-assist
Use when running PPC Assist Amazon PPC triage, interpreting PPC Assist metrics, reviewing search terms and suggestions, or preparing approval-gated account changes.
install-atom-eve-agent
Use when setting up or installing an existing Atom Eve AI agent into a project, including scaffolding a new eve.dev (Eve) or Flue app, adding an agent with the atom-eve CLI, wiring credentials, and verifying it runs. Triggers include "set up an Atom Eve agent", "install the SEO/ads/QA agent", "add an agent to this…
find-atom-eve-agent
Use when someone wants to find, browse, compare, or choose an Atom Eve AI agent for a task (SEO, ads, content, QA, analytics, research, CRO, support, finance, ops). Searches the Atom Eve registry and recommends the best-matching installable agent.