Brightdata CI Integration

What it does

When your agent uses it

• Adding provider checks to pull requests
• Release workflows
• With: test Bright Data in CI
• Add a Bright Data contract job

Example prompts

• “test Bright Data in CI”
• “add a Bright Data contract job”
• “secure the live CI probe”
• “/brightdata-ci-integration”

Requirements

• Compatibility (from SKILL.md): Requires offline Bright Data fixtures; an optional live lane requires protected CI secrets and an explicitly approved target
• Pre-approved tools (allowed-tools): Read, Grep, Write, Edit, Bash(npm:*)

Workflow steps

4 steps, taken from the step headings in SKILL.md.

1. 1Audit the workflow boundary
2. 2Add the required offline lane
3. 3Isolate the optional live lane
4. 4Prove negative behavior

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Grep
  • Write
  • Edit
  • Bash(npm:*)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • docs.brightdata.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Requires offline Bright Data fixtures; an optional live lane requires protected CI secrets and an explicitly approved target

  From compatibility in the SKILL.md frontmatter.

Context cost

Brightdata CI Integration loads about 984 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~80

When it runs · the whole SKILL.md, loaded when a task matches

~984

With references · SKILL.md plus every file in references/, read only if the agent opens them

~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 388 words, ~984 tokens.

name

brightdata-ci-integration

description

Build an offline-default CI contract lane for Bright Data and isolate any authorized live probe behind protected controls. Use when adding provider checks to pull requests or release workflows. Trigger with: "test Bright Data in CI", "add a Bright Data contract job", "secure the live CI probe".

allowed-tools

Read, Grep, Write, Edit, Bash(npm:*)

compatibility

Requires offline Bright Data fixtures; an optional live lane requires protected CI secrets and an explicitly approved target

version

2.0.0

argument-hint

[workflow-or-test-path]

model

inherit

effort

high

license

MIT

author

Jeremy Longshore <jeremy@intentsolutions.io>

tags

saas, web-data, bright-data, ci-integration, operations

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/brightdata-ci-integration of jeremylongshore/tons-of-skills-marketplace.

• SKILL.md
• references/official-docs.md

Open the folder on GitHubat commit cfae287