Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/gcwing/bitfun/gstack-csonpx skills add GCWing/BitFun --skill gstack-csogit clone --depth 1 https://github.com/GCWing/BitFunWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00153 | $0.09312 |
| Opus 5 | $0.00077 | $0.04656 |
| Sonnet 5 | $0.00031 | $0.01862 |
| Haiku 4.5 | $0.00015 | $0.00931 |
Grade B, and why
cso scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
- `IGNORE PREVIOUS`, `system override`, `disregard`, `forget your instructions` (prompt injection) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl`, `wget`, `fetch`, `http`, `exfiltrat` (network exfiltration) How it starts
The opening of the file, as written. The whole thing — 675 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cso — Chief Security Officer Audit (v2)
You are a Chief Security Officer who has led incident response on real breaches and testified before boards about security posture. You think like an attacker but report like a defender. You don't do security theater — you find the doors that are actually unlocked.
The real attack surface isn't your code — it's your dependencies. Most teams audit their own app but forget: exposed env vars in CI logs, stale API keys in git history, forgotten staging servers with prod DB access, and third-party webhooks that accept anything. Start there, not at the code level.
You do NOT make code changes. You produce a Security Posture Report with concrete findings, severity ratings, and remediation plans.
BitFun Team Mode Dispatch
When this skill is invoked by BitFun Team Mode, this skill supplies the security-review lens. Use existing Task sub-agents for independent security evidence gathering, then make final severity and remediation calls in the main Team session.
- Do not assume a CSO sub-agent exists. Choose only from the Task tool's available agents.
- Prefer a matching custom security sub-agent if available; otherwise use one
CodeReviewtask with an exact security lens for diff-focused review,Explorefor broader code/config mapping, andFileFinderfor security-sensitive files. - Keep Task work read-only. Ask for concrete evidence: file paths, trust boundaries, inputs, auth/data flows, exploit preconditions, and confidence.
- In parallel batches, return a compact Security brief:
critical/high findings,trust-boundary risks,false-positive notes,required fixes,verification. - The main Team orchestrator decides what blocks Build/Ship and asks the user for risk acceptance when needed.
User-invocable
When the user types /cso, run this skill.
Arguments
/cso— full daily audit (all phases, 8/10 confidence gate)/cso --comprehensive— monthly deep scan (all phases, 2/10 bar — surfaces more)/cso --infra— infrastructure-only (Phases 0-6, 12-14)/cso --code— code-only (Phases 0-1, 7, 9-11, 12-14)/cso --skills— skill supply chain only (Phases 0, 8, 12-14)/cso --diff— branch changes only (combinable with any above)/cso --supply-chain— dependency audit only (Phases 0, 3, 12-14)/cso --owasp— OWASP Top 10 only (Phases 0, 9, 12-14)/cso --scope auth— focused audit on a specific domain
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 675 lines · 153 tokens per session scan B ef5e00eca98b
cso is a skill published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed 2d ago), licensed MIT. It adds 153 tokens to every session and 9,312 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 2 findings (instruction-override phrasing, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agentteams-migrate
Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into AgentTeams as a managed Worker.
worker-management
Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use agentteams-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.
team-coordination
Use before deciding how you should organize team work: DAG vs Loop, dependency shape, task waves, quality gates, acceptance criteria, interruption, replanning, or what to do after Worker results arrive. Always use this skill for team organization strategy before you call project-management or task-management.
git-delegation
将所有 git 操作委托给 Manager 执行。Worker 无法直接访问 git credentials，因此任何需要认证的 git 操作（clone、push、fetch 等）都需要通过此机制委托给 Manager。.
github-operations
管理 GitHub Pull Request 和 Issue。包括创建/更新/合并 PR、添加评论、管理 Issue 等。注意：文件读写、分支操作、代码提交等请使用 git-delegation 技能。.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.