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/jessefmoore/offensive-claude-code/sliver-c2npx skills add jessefmoore/offensive-claude-code --skill sliver-c2git clone --depth 1 https://github.com/jessefmoore/offensive-claude-codeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jessefmoore/offensive-claude-code/sliver-c2)<a href="https://agentmods.dev/skills/jessefmoore/offensive-claude-code/sliver-c2"><img src="https://agentmods.dev/badge/skills/jessefmoore/offensive-claude-code/sliver-c2.svg" alt="Measured on agentmods" height="20"></a>What 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.00060 | $0.05027 |
| Opus 5 | $0.00030 | $0.02514 |
| Sonnet 5 | $0.00012 | $0.01005 |
| Haiku 4.5 | $0.00006 | $0.00503 |
Grade D, and why
sliver-c2 scanned grade D with 3 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
curl https://sliver.sh/install | sudo bash Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl https://sliver.sh/install | sudo bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://sliver.sh/install | sudo bash How it starts
The opening of the file, as written. The whole thing — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sliver C2
When to Activate
- You need a persistent C2 channel into a compromised host
- Transitioning from initial access (nxc/evil-winrm/psexec foothold) to a full C2 implant
- Running post-exploitation that requires in-memory .NET assembly execution, BOF, or process injection
- Setting up pivots through a compromised host to reach an internal subnet
- Any scenario where "interactive shell" is insufficient and you need a proper C2 beacon
Architecture Overview
┌─────────────────────────────────────────────────────────────────┐
│ Operator workstation │
│ sliver-client ──── mTLS/gRPC ──── sliver-server │
│ │ │
│ Listeners │
│ mTLS / HTTP(S) / DNS / WG │
│ │ │
│ Implants │
│ Session (interactive) │
│ Beacon (sleep/callback) │
└─────────────────────────────────────────────────────────────────┘
Implant types:
| Type | Behaviour | OPSEC |
|---|---|---|
| Session | Persistent interactive connection | Noisier — long-lived TCP connection |
| Beacon | Sleeps, calls back on interval, queues tasks | Preferred — mimics normal traffic, harder to detect |
1 — Server Setup
Install (Kali / Debian)
curl https://sliver.sh/install | sudo bash
# Installs: /usr/local/bin/sliver-server /usr/local/bin/sliver-client
Start server
# Interactive (foreground)
sudo sliver-server
# Daemon mode (recommended for engagements)
sudo sliver-server daemon
Connect as operator (same host)
sliver-client
# Defaults to ~/.sliver/configs/default.cfg if present
2 — Multiplayer Mode (team engagements)
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.
- 4d ago First seen · 646 lines · 60 tokens per session scan D 532a6f84c043
sliver-c2 is a skill published in the GitHub repository jessefmoore/offensive-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 5,027 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…