Vulnerability Scanning
sickn33/agentic-awesome-skills
Scan systems and dependencies for CVEs and security vulnerabilities.
A skill your agent uses when building vulnerability-based trust through quarterly team exercises from the EOS Trust Builders toolbox
$ npx skills add bradfeld/ceos --skill ceos-trust -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bradfeld/ceos ceos-trust --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ceos-trust .claude/skills/ceos-trust && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ceos-trust" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-trust into .claude/skills/ceos-trust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-trust", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bradfeld/ceos/tree/main/skills/ceos-trustType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bradfeld/ceos --skill ceos-trust -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bradfeld/ceos ceos-trust --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ceos-trust .agents/skills/ceos-trust && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ceos-trust" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-trust into .agents/skills/ceos-trust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-trust", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bradfeld/ceos --skill ceos-trust -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bradfeld/ceos ceos-trust --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ceos-trust .cursor/skills/ceos-trust && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ceos-trust" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-trust into .cursor/skills/ceos-trust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-trust", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bradfeld/ceos.git --path skills/ceos-trust--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bradfeld/ceos --skill ceos-trust -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bradfeld/ceos ceos-trust --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ceos-trust .gemini/skills/ceos-trust && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ceos-trust" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-trust into .gemini/skills/ceos-trust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-trust", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bradfeld/ceos ceos-trustInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bradfeld/ceos --skill ceos-trust -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ceos-trust .github/skills/ceos-trust && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ceos-trust" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-trust into .github/skills/ceos-trust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-trust", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bradfeld/ceos --skill ceos-trust -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bradfeld/ceos ceos-trust --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bradfeld/ceos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ceos-trust .opencode/skills/ceos-trust && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ceos-trust" agent skill from https://github.com/bradfeld/ceos/tree/main/skills/ceos-trust into .opencode/skills/ceos-trust/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ceos-trust", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ceos-trustA skill your agent uses when building vulnerability-based trust through quarterly team exercises from the EOS Trust Builders toolbox
Ceos Trust is an agent skill from bradfeld/ceos. Use when building vulnerability-based trust through quarterly team exercises from the EOS Trust Builders toolbox
Its SKILL.md is about 6.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: EOS (Entrepreneurial Operating System) skills for Claude Code. Run your business on EOS with AI. The licence is MIT.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit bdd5f01. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ceos Trust loads about 6.6k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 3,313 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from bradfeld/ceos at commit bdd5f01, republished under its MIT licence (© bradfeld). 3,313 words, ~6,594 tokens.
.claude/skills/ceos-trust/SKILL.md (or your agent's skills folder).Facilitate the 10 Trust Builder exercises from the EOS Toolbox, progressing from low to high vulnerability. Acts as a facilitation guide — providing instructions, timing, debrief questions, and recording outcomes — rather than trying to replicate exercises digitally. Teams typically do one exercise per quarter, building deeper trust over time. Drawn from Patrick Lencioni's "Five Dysfunctions of a Team" framework.
Not for: People evaluation (use ceos-people), organizational health assessment (use ceos-checkup), or performance conversations (use ceos-quarterly). The Trust Builders are team-level exercises focused on vulnerability-based trust, not individual assessment.
Search upward from the current directory for the .ceos marker file. This file marks the root of the CEOS repository.
If .ceos is not found, stop and tell the user: "Not in a CEOS repository. Clone your CEOS repo and run setup.sh first."
Sync before use: Once you find the CEOS root, run git -C <ceos_root> pull --ff-only --quiet 2>/dev/null to get the latest data from teammates. If it fails (conflict or offline), continue silently with local data.
| File | Purpose |
|---|---|
data/trust/ | Exercise records — one file per completed exercise |
templates/trust-exercise.md | Template for recording exercise outcomes |
data/accountability.md | Team composition for participant suggestions (read-only — use ceos-accountability to modify) |
data/checkups/ | Organizational Checkup scores for trust cross-reference (read-only — use ceos-checkup to modify) |
| # | Exercise | Vulnerability | Time Box | Description |
|---|---|---|---|---|
| 1 | Personal Histories | Low | 30-45 min | Each team member shares personal background (hometown, family, first job, hobbies) |
| 2 | DISC/Kolbe Profiles | Low | 45-60 min | Share and discuss personality/working style assessment results |
| 3 | Lifeline Exercise | Medium | 45-60 min | Map significant life events on a timeline, share with the team |
| 4 | One Thing | Medium | 20-30 min | Each person shares one thing the team doesn't know about them |
| 5 | Feedback Round | Medium | 45-60 min | Structured positive and constructive feedback for each team member |
| 6 | Strengths Spotlight | Medium | 30-45 min | Each person identifies their top strengths, team validates and adds |
| 7 | Conflict Norms | Medium-High | 45-60 min | Establish how the team will handle disagreement and conflict |
| 8 | Accountability Partners | Medium-High | 30-45 min | Pair up for mutual accountability check-ins between meetings |
| 9 | Team Effectiveness Debrief | High | 60-90 min | Rate and discuss how the team works together as a unit |
| 10 | Vulnerability Circle | High | 30-60 min | Share a current struggle, fear, or area where you need help |
| Level | Exercises | What It Means |
|---|---|---|
| Low | 1-2 | Safe sharing — factual information, low personal risk |
| Medium | 3-6 | Personal sharing with moderate risk — life events, feedback, strengths |
| Medium-High | 7-8 | Navigating conflict and accountability — requires existing trust |
| High | 9-10 | Deep vulnerability — honest assessment of team and personal struggles |
Each completed exercise is a markdown file at data/trust/YYYY-MM-DD-exercise-slug.md with YAML frontmatter:
date: "2026-02-16"
exercise_number: 1
exercise_name: "Personal Histories"
participants: ["Brad Feld", "Daniel"]
facilitator: "Brad Feld"
duration_minutes: 35
vulnerability_level: low
status: completeFile naming: YYYY-MM-DD-exercise-slug.md — date prefix for chronological ordering, exercise slug identifies the type.
| # | Exercise | Slug |
|---|---|---|
| 1 | Personal Histories | personal-histories |
| 2 | DISC/Kolbe Profiles | disc-kolbe-profiles |
| 3 | Lifeline Exercise | lifeline-exercise |
| 4 | One Thing | one-thing |
| 5 | Feedback Round | feedback-round |
| 6 | Strengths Spotlight | strengths-spotlight |
| 7 | Conflict Norms | conflict-norms |
| 8 | Accountability Partners | accountability-partners |
| 9 | Team Effectiveness Debrief | team-effectiveness-debrief |
| 10 | Vulnerability Circle | vulnerability-circle |
Use when guiding the team through the next Trust Builder exercise. This is the primary mode — one exercise per session.
Read all files from data/trust/ via Glob("data/trust/*.md"). Parse YAML frontmatter to find completed exercises by exercise_number.
Determine the next exercise in sequence (lowest number not yet completed).
Display the recommendation:
Next Trust Builder: #N [Name]
Vulnerability level: [low/medium/high]
Time box: [N-N] minutes
Last exercise: #[N-1] [Name] on [date]
Ready to facilitate?For medium or higher vulnerability exercises (3+): "This is a [level]-vulnerability exercise. Ensure the team has completed the earlier exercises and the environment feels psychologically safe."
For exercise #2 (DISC/Kolbe Profiles): "Note: Participants should have completed their DISC and/or Kolbe assessments before this exercise. Has everyone taken their assessments?"
For exercise #5 (Feedback Round): "Note: This exercise involves giving and receiving direct feedback. Remind the team that feedback should be specific, actionable, and delivered with positive intent."
For exercise #7+ (Medium-High and High): "This exercise requires a foundation of trust from earlier exercises. If the team hasn't built that foundation, consider revisiting exercises 1-6 first."
Read data/accountability.md to identify leadership team members. Suggest them as participants.
"Who is participating? (Default: leadership team from Accountability Chart)"
Allow the user to confirm or modify the participant list.
Display the exercise-specific facilitation guide based on the exercise number. Each exercise follows this structure:
Purpose → Setup → Steps → Time Management → Debrief Questions
Exercise 1: Personal Histories
Purpose: Break down barriers by sharing personal backgrounds. This is the foundation — it humanizes teammates beyond their work roles.
Setup: Gather the team in a comfortable setting. No notes needed. Go around the table.
Steps:
Time Management: 3-5 min per person + 10 min debrief. For a team of 6: ~40 minutes total.
Debrief Questions:
Exercise 2: DISC/Kolbe Profiles
Purpose: Understand each other's working styles to improve communication and reduce friction.
Setup: All participants must have completed their DISC and/or Kolbe assessments beforehand. Print or display results.
Steps:
Time Management: 5 min per person + 15-20 min group discussion.
Debrief Questions:
Exercise 3: Lifeline Exercise
Purpose: Build deeper understanding by sharing the significant events that shaped who you are.
Setup: Give each person a blank piece of paper. Draw a horizontal line (the lifeline) from birth to present. Mark significant events above the line (positive) and below the line (negative/challenging).
Steps:
Time Management: 10 min prep + 8 min per person + 10 min debrief.
Debrief Questions:
Exercise 4: One Thing
Purpose: A quick exercise to build on existing trust by sharing something new and personal.
Setup: Simple round-table format. No preparation needed.
Steps:
Time Management: 3 min per person + 5 min debrief.
Debrief Questions:
Exercise 5: Feedback Round
Purpose: Practice giving and receiving honest feedback in a structured, safe format.
Setup: Each person will give feedback to every other team member. Prepare by thinking about one strength and one area for growth per person.
Steps:
Time Management: For a team of N, each round takes ~3 min × (N-1) people giving feedback + 2 min transition. Total: roughly 5-8 min per focus person.
Debrief Questions:
Exercise 6: Strengths Spotlight
Purpose: Reinforce what each person does best and ensure the team leverages individual strengths.
Setup: Each person prepares a list of their top 3-5 personal strengths before the session.
Steps:
Time Management: 5-7 min per person + 10 min debrief.
Debrief Questions:
Exercise 7: Conflict Norms
Purpose: Establish explicit agreements for how the team will handle disagreement, preventing unhealthy conflict patterns.
Setup: Whiteboard or shared document. This is a group discussion, not individual sharing.
Steps:
Time Management: 45-60 minutes for the full exercise.
Debrief Questions:
Exercise 8: Accountability Partners
Purpose: Create peer-to-peer accountability relationships that supplement the formal meeting structure.
Setup: Pair team members. Consider pairing people who don't work closely together or who have complementary strengths.
Steps:
Time Management: 30-45 minutes total.
Debrief Questions:
Exercise 9: Team Effectiveness Debrief
Purpose: Honestly assess how the team functions as a unit — what's working, what isn't, and what needs to change.
Setup: Each person independently rates the team on 5 dimensions (1-5 scale) before the session:
(These map to Lencioni's Five Dysfunctions pyramid.)
Steps:
Time Management: 60-90 minutes. This is the most substantive exercise.
Debrief Questions:
Exercise 10: Vulnerability Circle
Purpose: The deepest trust exercise — each person shares a current struggle, fear, or area where they need support.
Setup: This exercise requires strong existing trust. Ensure exercises 1-9 have been completed. Set the tone: "This is a safe space. What's shared here stays here. Our only job is to listen and support."
Steps:
Time Management: 5-8 min per person + 15 min debrief. For a team of 6: ~50-60 minutes.
Debrief Questions:
After the exercise is complete, ask the user for:
Create a new file from templates/trust-exercise.md at data/trust/YYYY-MM-DD-exercise-slug.md. Fill in all frontmatter fields and body sections.
Show the complete file before writing. Ask: "Save this trust exercise record?"
After saving, display:
Exercise #N [Name] complete!
Progression: N/10 exercises completed
Next: #[N+1] [Name] ([vulnerability level])
Recommended timing: Next quarter (~90 days)
Trust exercises build on each other. The next exercise
will go deeper — schedule it for your next quarterly session.Use when checking which exercises have been completed, what's next, and whether the team is on cadence.
Read all files from data/trust/ via Glob("data/trust/*.md"). Parse YAML frontmatter.
If no files exist: "No trust exercises recorded yet. Start with Exercise #1: Personal Histories using Facilitate mode."
Trust Builders — Progression
━━━━━━━━━━━━━━━━━━━━━━━━━━━
| # | Exercise | Level | Status | Date | Participants |
|---|----------|-------|--------|------|-------------|
| 1 | Personal Histories | Low | ✓ Done | 2026-01-15 | Brad, Daniel |
| 2 | DISC/Kolbe Profiles | Low | ✓ Done | 2026-04-10 | Brad, Daniel |
| 3 | Lifeline Exercise | Medium | → Next | — | — |
| 4 | One Thing | Medium | Pending | — | — |
| ... | ... | ... | ... | ... | ... |
| 10 | Vulnerability Circle | High | Pending | — | — |
Progress: 2/10 exercises (20%)
██████░░░░░░░░░░░░░░░░░░ 20%Calculate days since most recent exercise.
Optionally read data/checkups/ for the most recent organizational checkup. Look for Question 11 score (leadership trust question).
If no checkup data exists, skip this step silently.
Use when reviewing the history of trust exercises — dates, participants, key takeaways, and progression over time.
Read all files from data/trust/ via Glob("data/trust/*.md"). Parse YAML frontmatter.
If no files exist: "No trust exercises recorded yet. Start with Exercise #1: Personal Histories using Facilitate mode."
Show all completed exercises chronologically:
Trust Builders — Exercise History
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| Date | # | Exercise | Level | Duration | Participants | Key Takeaway |
|------|---|----------|-------|----------|-------------|-------------|
| 2026-01-15 | 1 | Personal Histories | Low | 35 min | Brad, Daniel | Discovered shared background in... |
| 2026-04-10 | 2 | DISC/Kolbe Profiles | Low | 50 min | Brad, Daniel | Brad is high-D, Daniel is high-I... |Progression Summary:
Completed: N/10 exercises
Current cycle: 1 (exercises 1-10)
Exercises by vulnerability level:
Low (1-2): N completed
Medium (3-6): N completed
Medium-High (7-8): N completed
High (9-10): N completed
Avg time between exercises: [N] days
Total time invested: [N] minutes across [N] exercisesIf all 10 exercises are complete:
🎉 Cycle 1 Complete!
All 10 Trust Builder exercises have been completed.
Consider starting Cycle 2 — repeating exercises builds deeper trust.
Many teams report that exercises hit differently the second time around,
especially as the team evolves and new members join.If the team has completed multiple cycles, show cycle-over-cycle comparison.
Ask: "Want to view the full record for a specific exercise?"
If yes, read and display the complete file for the requested exercise.
Facilitate: Exercise-specific facilitation guide with purpose, setup, steps, time management, and debrief questions. Outcome record shown before save. Post-exercise summary with next exercise recommendation.
Schedule: Progression table showing all 10 exercises with completion status, staleness warnings, and checkup trust score cross-reference. Visual progress bar.
Review: Chronological history table with dates, exercises, levels, durations, and key takeaways. Progression summary by vulnerability level. Cycle status.
data/accountability.md — seat names, owners, team membersdata/checkups/ — organizational health assessment scoresOnly ceos-trust writes to data/trust/. Other skills may reference trust exercise data for team health context, but do not modify exercise records.
© bradfeld, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/ceos-trust of bradfeld/ceos.
Open the folder on GitHubat commit bdd5f01
Ceos Trust next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ceos Trust this skillbradfeld/ceos | 156 | — | ~6.6k | Automated safety check: Pass | MIT | |
| Vulnerability Scanningsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Performing Vulnerability Scanning With Nessusmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Building Vulnerability Scanning Workflowmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Performing Ot Vulnerability Assessment With Clarotymukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Cra Vulnerability Obligationsdavila7/claude-code-templates | 32k | 1 repos | ~4.5k | Automated safety check: Pass | CC-BY-4.0 |
sickn33/agentic-awesome-skills
Scan systems and dependencies for CVEs and security vulnerabilities.
mukul975/Anthropic-Cybersecurity-Skills
Performs authenticated and unauthenticated vulnerability scanning using Tenable Nessus to identify known vulnerabilities, misconfigurations, default credentials, and missing patches across network…
mukul975/Anthropic-Cybersecurity-Skills
Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure.
mukul975/Anthropic-Cybersecurity-Skills
Perform OT vulnerability assessments using the Claroty xDome platform for asset discovery, risk scoring, and vulnerability correlation, combining passive traffic-based identification and active safe…
davila7/claude-code-templates
A skill your agent uses when a user asks what the EU Cyber Resilience Act (CRA) means for their product, whether and when they must report a vulnerability or incident, or what a specific CVE…
warpdotdev/warp
Gathers security findings from Dependabot, GCP container scanning, Docker Scout and Linear security issues, then triages and remediates them across Warp's repos and images.
bradfeld/ceos
A skill your agent uses when viewing, updating, or auditing the Accountability Chart — seats, owners, and roles
bradfeld/ceos
A skill your agent uses when managing daily operational delegation through The Stack and structured leader-assistant standups
bradfeld/ceos
A skill your agent uses when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
bradfeld/ceos
A skill your agent uses when assessing and optimizing the 8 financial levers that drive cash flow and profitability
bradfeld/ceos
A skill your agent uses when taking a Clarity Break — stepping back from day-to-day work for strategic thinking time
bradfeld/ceos
A skill your agent uses when you want a quick snapshot of overall business health across all EOS components
A skill your agent uses when building vulnerability-based trust through quarterly team exercises from the EOS Trust Builders toolbox. Ceos Trust is an agent skill from bradfeld/ceos.
Ceos Trust fits situations like: building vulnerability-based trust through quarterly team exercises from the EOS Trust Builders toolbox.
Run `npx skills add bradfeld/ceos --skill ceos-trust -a claude-code`. Or copy the skill folder (skills/ceos-trust in bradfeld/ceos) into .claude/skills/ceos-trust in your project. Claude Code loads it when a task matches its description.
Run `npx skills add bradfeld/ceos --skill ceos-trust -a codex`. Or copy the skill folder (skills/ceos-trust in bradfeld/ceos) into .agents/skills/ceos-trust in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bradfeld/ceos --skill ceos-trust -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ceos-trust, .gemini/skills/ceos-trust, .github/skills/ceos-trust and .opencode/skills/ceos-trust in your project.
Going by SKILL.md and its folder, Ceos Trust needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Ceos Trust is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.6k tokens (SKILL.md is roughly 26k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Ceos Trust: Vulnerability Scanning (sickn33/agentic-awesome-skills, 47k stars), Performing Vulnerability Scanning With Nessus (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Building Vulnerability Scanning Workflow (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Performing Ot Vulnerability Assessment With Claroty (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
bradfeld (a GitHub user) maintains it in bradfeld/ceos, which has 156 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on September 13, 2026.
Source: bradfeld/ceos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.