Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Copilot CLI
v1.1.1Reference knowledge base for GitHub Copilot CLI. Use when answering questions about Copilot CLI features, commands, configuration, plugins, hooks, skills, MC...
⭐ 1· 125·0 current·0 all-time
bySagar Awale@awalesagar
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name, description, required binary (copilot), and the npm install (@github/copilot) align with a Copilot CLI reference skill — the install spec and OS targets are appropriate for the stated purpose.
Instruction Scope
SKILL.md formally instructs the agent/operator to edit and read user config files (~/.copilot/config.json), session stores (~/.copilot/session-state/...), logs, add MCP servers/plugins, pre-trust directories, and to run programmatic invocations with flags that enable unattended, persistent behavior. Those runtime actions access user files/state beyond the declared requires.config_paths and could cause persistent changes; the skill does not explicitly declare or constrain that file access.
Install Mechanism
Install via the npm package @github/copilot is a standard, expected mechanism for providing the copilot binary; this is a traceable public registry package rather than an arbitrary download, so install risk is moderate and proportional.
Credentials
The skill declares no required env vars, but the docs reference multiple sensitive env vars (COPILOT_GITHUB_TOKEN, GH_TOKEN, COPILOT_MODEL, COPILOT_HOME, etc.) and show CI examples that use PATs. The instructions suggest using/setting tokens and persistent config entries (trusted_folders) without declaring or limiting credential access, which can lead to broad capability when combined with automation flags.
Persistence & Privilege
always:false (no forced global inclusion) and no cross-skill config modifications are declared, but the docs explicitly guide persistent changes (editing config.json, installing plugins, adding MCP servers, pre-trusting folders) and recommend automation flags (--no-ask-user, --allow-all, --yolo) that enable long-lived agent actions; users should be aware these actions grant ongoing privileges if applied.
What to consider before installing
This is a documentation/reference skill for Copilot CLI and mostly makes sense, but it instructs editing user config and using environment tokens and automation flags that give persistent, broad capabilities. Before installing or following the examples: (1) confirm the npm package (@github/copilot) is the official publisher and inspect the package if you can; (2) avoid pre-trusting your real home/project directories — test in an isolated/temp directory or container; (3) do not place long-lived PATs in shared environments; prefer minimal-scoped CI tokens and ephemeral credentials; (4) avoid running programmatic invocations with --allow-all / --yolo / --no-ask-user unless you trust the code and environment; (5) review any repo hooks/plugins before installing them. If you want lower risk, install and exercise the CLI in a sandboxed VM or container and keep COPILOT_HOME pointed to a separate directory.Like a lobster shell, security has layers — review code before you run it.
latestvk97f9t88c6jj169fyj38nks1x184jc5s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
⌨️ Clawdis
OSmacOS · Linux · Windows
Binscopilot
Install
Install via npm
Bins: copilot
npm i -g @github/copilot