Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Research.Deprecation Usage

skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b

★ 506pushed 7 days ago
!CAUTIONGrade B · 89/100 · 2 findings · a03fbe3
506repo stars · whole coinbase/cds

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: Audits how often deprecated CDS exports are actively used in customer codebases using Sourcegraph MCP search tools. Use this skill whenever asked to assess removal readiness for deprecated CDS APIs, investigate the…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Research.Deprecation Usage (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/research-deprecation-usage

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high2 medium0 low0 info

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

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN2
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (2)

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/.claude/skills/research.deprecation-usageThe 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: Audits how often deprecated CDS exports are actively used in customer codebases using Sourcegraph MCP search tools. Use this skill whenever asked to assess removal readiness for deprecated CDS APIs, investigate the…

---
name: research.deprecation-usage
description: |
  Audits how often deprecated CDS exports are actively used in customer codebases using Sourcegraph MCP search tools.
  Use this skill whenever asked to assess removal readiness for deprecated CDS APIs, investigate the
  blast radius of removing a deprecated component or hook, check Sourcegraph for customer usage of
  deprecated exports, or help the team decide which deprecated APIs are safe to remove in the next
  major version. Always invoke when asked to "audit deprecated APIs", "check Sourcegraph for deprecated
  usage", "find usages of deprecated exports", "analyze deprecation impact", or any similar request
  involving CDS deprecations and customer adoption.
---

## Objective

Your objective is to provide information to user about the extent to which deprecated members of CDS are used in customer repositories. This information should be as accurate as possible as it will be used to inform decisions on whether or not it is safe to drop certain exports in a release or hold them for the next major version.

**Removal readiness policy:** a deprecated API must remain for **one full major version undisturbed** before removal. If it was deprecated during major `M`, it must survive all of `M+1`; the earliest removal major is `M+2` (see `@deprecationExpectedRemoval` and `.claude/skills/deprecate-cds-api/SKILL.md`).

Follow the

## 1 - Determining Research Scope

You may be asked to investigate a single, specific deprecation or all CDS deprecations in general.

If you need to perform a comprehensive audit, there is one additional preparation step:

```bash
yarn node scripts/findDeprecations.mjs --json
```

This script extracts the deprecations with metadata from all CDS packages in JSON format.

### 2 - Determining the Type of Deprecation

There are two common categories of deprecations in CDS packages:

1. A single prop of a React component
2. A whole React component, function or constant

If you are researching a single deprecation, find it in this monorepo's source code (DO NOT USE SOURCEGRAPH). It will be marked with the jsdoc `@deprecated` annotation. Inspect the code around the deprecation to determine which of the two categories it falls into. If the deprecation is found in multiple CDS packages you may ask the user to clarify which package is of interest to them.

If you are performing a comprehensive audit for all CDS deprecations, the output of the script you ran in Step 1 will have already classified the deprecaations for you.

## 3 - Using Sourcegraph

For every deprecation you must research, perform a search on Sourcegraph to find evidence of usage.

**IMPORTANT:** Only attempt to search for one deprecation at a time.

**IMPORTANT:** Do not attempt to search if you do not have the information to

You must perform a `keyword search` using the Sourcegraph MCP server. For the `query` parameter you must use the EXACT queries I share below, substituing in the name(s) of the deprecation you are investigating.

### Components, Functions, Constants

Replace `NAME_HERE` with the name of the deprecated component/function/constant

```
NOT repo:frontend/cds(-(internal|public|next))?$ file:..(t|j)sx?$ /import[^;'"]*?\bNAME_HERE\b[^;'"]*?from\s+['"][^'"]*(?:cds-web|cds-mobile)[^'"]*['"]/
```

### React prop

Replace `NAME_HERE` with the name of the React component and `PROP_HERE` with the name of the deprecated prop.

```
NOT repo:frontend/cds(-(internal|public|next))?$ file:..(t|j)sx?$ /<\\s*NAME_HERE\\b[^>]*?\\s+PROP_HERE[\\s=\/>]/
```

## 4 - Structured Output

Your output will depend on the number of deprecations you needed to audit:

### Single Deprecation Output

State the total number of usages found and output a markdown table with columns: Repo, Hits, Search Link — where each link uses a full Sourcegraph URL that will take the user directly to the relevant regex search for the deprecation, filtered by the repo represented in the row of the table.

### How to build per-repo Sourcegraph search

For the following sourcegraph search:

```
/<\\s*CellMedia\\b[^>]*\\stitle[\\s=\\/>]/ NOT repo:frontend/cds(-(internal|public|next))?$ file:\\.(t|j)sx?$
```

Here is an example for repo coinbase.ghe.com/payments/onramp-widget:

`https://sourcegraph.cbhq.net/search?q=NOT+repo%3Afrontend%2Fcds%28-%28internal%7Cpublic%7Cnext%29%29%3F%24+file%3A..%28t%7Cj%29sx%3F%24+%3C%5Cs*CellMedia%5Cb%5B%5E%3E%5D*%3F%5Cs%2Btitle%5B%5Cs%3D%2F%3E%5D&patternType=regexp&sm=0&__cc=1&df=%5B%22repo%22%2C%22coinbase.ghe.com%2Fpayments%2Fonramp-widget%22%2C%22repo%3A%5Ecoinbase%5C%5C.ghe%5C%5C.com%2Fpayments%2Fonramp-widget%24%22%5D`

### Multiple Deprecations Output

When you have analyzed more than one deprecation, simply list out every deprecation and the total number of matches that came back from its sourcegraph query.

Excerpt, first 4,831 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

Download folder ↗
git clone https://github.com/coinbase/cds
git -C cds checkout a03fbe3db14b

The author documents no install command, so this uses the repository directly. Our verdict covers commit a03fbe3db14b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. !CAUTION B 89 / 100

    first audit · source a03fbe3db14b

Questions about Research.Deprecation Usage

What does the Research.Deprecation Usage skill do?
Coinbase Design System
Is Research.Deprecation Usage safe to install?
With care. The audit graded it B (89/100) and found 2 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Research.Deprecation Usage access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (a03fbe3db14b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

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.