Agent skill · Audited from source
Cds Code
skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b
Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit a03fbe3db14b and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 2 findings, 0 critical or high. What it does: Provides a workflow for building and reviewing high-quality React and React Native UI with the Coinbase Design System (CDS). Use this skill to create UI or make visual changes to existing UI with CDS components, tokens,…
Cite
Cite this page
ModelsAtlas. “Cds Code (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/cds-code
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 2 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | PASS | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (2)
MEDIUMInventory / provenanceinv.symlink · .claude/skills/git.resolve-version-conflicts
.claude/skills/git.resolve-version-conflicts
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/skill-creator
.claude/skills/skill-creator
- Why
- link not followed
- Fix
- —
Audit 0.4.1 · source sha a03fbe3db14b · 14 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishercoinbase GitHub organizationOwner of the repository this skill is read from
- Source foldercoinbase/cds/skills/cds-codeThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdicta03fbe3db14bA new audit runs when the source changes
- Repository statusNot archivedLast push 7 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Provides a workflow for building and reviewing high-quality React and React Native UI with the Coinbase Design System (CDS). Use this skill to create UI or make visual changes to existing UI with CDS components, tokens,…
--- name: cds-code description: | Provides a workflow for building and reviewing high-quality React and React Native UI with the Coinbase Design System (CDS). Use this skill to create UI or make visual changes to existing UI with CDS components, tokens, style props, icons, and illustrations. Use it for explicit CDS-adherence audits and reviews, not non-visual logic, data, analytics, navigation, tests, generated code, or refactoring. Examples: "build this screen", "fix spacing on this component", "replace this UI with CDS components", "perform a CDS audit on our changes", "check our codebase for CDS adherence", "does this feature use CDS well?" license: Apache-2.0 metadata: version: '2.2.0' --- # CDS Code Skill ## On every request Before responding, determine what the user needs: **Coding** — the user wants to create new UI or make visual changes to existing UI with CDS → follow the Coding Workflow. **Review** — the user explicitly asks to audit, review, or check existing code for CDS adherence → read `guidelines/code-review.md` and follow it instead. **Out of scope** — the user wants non-visual work such as business logic, data handling, analytics, navigation wiring, tests, generated code, or refactoring → do not follow this skill's coding or review workflows. **Default in-scope work to coding.** Only treat the user's request as a review or audit if the intent is explicit. Building or updating UI is the primary use case for this skill. ## Initialization Run this once per session, before doing anything else. Run the discovery script: `scripts/discover-cds-packages.sh` Its output tells you: - The `CDS Runtime` (`web` or `mobile`) — use this value as the `platform` argument for the CDS MCP server if it is needed. - Every installed CDS package: its name, version, and valid export subpaths — these import paths are the ONLY ALLOWED PATHS when importing from CDS packages If the script cannot be run, much of the information it provides can be determined via manual inspection: - Infer the platform by inspecting existing CDS imports in the project's source code - Find valid import paths by reading the `exports` field of the `package.json` of installed CDS packages in `node_modules` ## Coding Workflow For in-scope coding tasks, follow these steps in order. **YOU MUST** perform steps 1 and 2 before writing any code! ### Step 1: Prepare CDS documentation For any CDS documentation needs, use either of the following tools. If neither are available, let the user know but continue — documentation is helpful but not required. - Activate the `cds-docs` skill OR... - If the `cds-docs` skill is not configured, try calling the CDS MCP server `list-cds-routes` tool. Then read the platform-specific docs (using the runtime detected in Initialization): - `getting-started/styling` - `getting-started/theming` ### Step 2: Identify the appropriate components Use `guidelines/components.md` to help identify the appropriate CDS components for the task. The guidelines file will cover most use cases, but you may optionally browse the CDS docs for the full list of supported CDS components. If you decide your task will require icons (`Icon` or `IconButton`) or illustrations (`SpotSquare`, `Pictogram`, `HeroSquare`, etc.) please read the corresponding guidelines files for more details. | Icons | Illustrations | | --------------------- | ----------------------------- | | `guidelines/icons.md` | `guidelines/illustrations.md` | If no CDS component fits your use case, you may fall back to the following options in this order of priority: 1. search for a relevant and reusable React component from the project's codebase to use 2. build your own custom React component using CDS primitives as building blocks 3. use the native platform's JSX elements (div, View, etc.) for bespoke UI as a last resort **IMPORTANT:** Always inform the user which CDS components you are planning to use before moving on to Step 3. ### Step 3: Optionally read component docs For any CDS component you plan to use, retrieve and read their documentation (see Step 1 in this workflow for more details on docs setup). If documentation is not retrievable for any reason, the published type definitions for the component may be used to determine the full props API a component affords. This is no substitute for reading the documentation, but it can be a useful fallback when documentation is not available. ### Step 4: Execute the task (writing code) Now create or update the UI with proper CDS components and usage. #### Package scope The package name may vary between projects. Different repos may install CDS under different scopes. Always match the full CDS package name(s) as determined in the initialization step. If the project already has CDS imports in existing code, match whatever scope those files use. #### Using the Design System In most cases, you should avoid using inline style objects or CSS classNames (web only). Through these methods it is very easy to make common mistakes like using hardcoded property values instead of the CDS design tokens. Doing so would break the component's connection to the CDS theme. If you must use a style object or a CSS className, you can still access the CDS theme either through the `useTheme` hook or by CSS variables (web only). Most CDS components implement an API that conveniently allows you to apply CDS design tokens, internally we call these 'style props'. In cds-web, style props essentially act as an API for applying atomic CSS classes, much like Tailwind's utility classes which are so prevelant in the web ecosystem. You should prefer setting these style props for styling components over setting custom style via inline styles or CSS. **Why this matters:** When you set `font`, `color`, `textAlign`, or other typography properties through `style` instead of props, the component loses its connection to the CDS theme. For example, setting `fontSize
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit a03fbe3
npx skills add https://github.com/coinbase/cds --skill cds-docs npx skills add https://github.com/anthropics/skills --skill skill-creator
git clone https://github.com/coinbase/cds git -C cds checkout a03fbe3db14b
Commands as the repository documents them: shown, never run by us. Our verdict covers commit a03fbe3db14b only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Cursor | Mentioned in its text, not tested | Skills for Cursor · About Cursor |
Audit history
Every audit, every source change
- !CAUTION B 89 / 100
first audit · source
a03fbe3db14b
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/coinbase/cds-code/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
mattpocock/skills
Implement a piece of work based on a spec or set of tickets.
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
mattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
Add this badge to your README
[](https://modelsatlas.com/skills/coinbase/cds-code/)
<a href="https://modelsatlas.com/skills/coinbase/cds-code/"><img src="https://modelsatlas.com/skills/coinbase/cds-code/badge.svg" alt="ModelsAtlas: CAUTION B"></a>
Questions about Cds Code
What does the Cds Code skill do?
Is Cds Code safe to install?
What can Cds Code access on my machine?
Which assistants does Cds Code work with?
How current is this page?
Sources
- github.com/coinbase/cds/tree/master/skills/cds-code — the audited source at commit a03fbe3db14b and every finding aboveObserved · 14 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Cds Code skill do?
- Is Cds Code safe to install?
- What can Cds Code access on my machine?