ccs-experiments
Use when designing or auditing ACM CCS experiments, attack demonstrations, adaptive-attack defense evaluations, security measurements, baselines, overhead and cost reporting, ablations, and claim-to-evidence fit, with emphasis on evidence that survives an adversarial program committee rather than le…
Install / Use
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-experimentsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of ccs-experiments
ccs-experiments scores 83/100 on our quality scale, 911th of 1,096 Security skills we index.
Its SKILL.md is 3.7 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.
With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ccs-experiments is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ccs-experiments compared with similar skills
All 4 of these similar skills score higher than ccs-experiments; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ccs-experiments (this skill)by brycewang-stanford | 83 | 1.2k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
Frequently asked questions
- How do I install ccs-experiments?
- Run
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-experiments. The install tabs above show the steps for each supported agent. - Which AI agents does ccs-experiments work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ccs-experiments safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ccs-experiments still maintained?
- The repository was last updated about 2 months ago, so ccs-experiments is actively maintained.
Skill content
View source on GitHubname: ccs-experiments description: Use when designing or auditing ACM CCS experiments, attack demonstrations, adaptive-attack defense evaluations, security measurements, baselines, overhead and cost reporting, ablations, and claim-to-evidence fit, with emphasis on evidence that survives an adversarial program committee rather than leaderboard wins.
CCS Experiments
Use this before submission when the attack demonstration, defense evaluation, or measurement story is not yet locked.
Experiment audit
- Map each security claim to a specific artifact: an exploit run, an overhead measurement, a coverage number, a false-positive/false-negative table, or a measurement dataset.
- For attacks, demonstrate the exploit against a realistic, named target (software version, platform, configuration) and report the resource cost to the attacker.
- For defenses, evaluate against an adaptive attacker built with knowledge of the defense, and report performance overhead, memory cost, and any compatibility breakage.
- For measurements, validate sampling: document the population, the vantage point, coverage and blind spots, and ground-truth checks against known cases.
- Include baselines that represent the state of the art in attack or defense, not strawmen.
- Report variance for stochastic results and audit for leakage, selection bias, and any mismatch between the threat model and the tested configuration.
What experiments are for at this venue
- CCS experiments exist to make a security claim undeniable to a skeptic, not to top a benchmark. One clean end-to-end exploit against a real target outweighs a table of micro-benchmarks.
- The strongest defense design triad: the attack it stops, an adaptive attack that knows the defense, and a deployment-cost measurement. Missing the middle element is the classic CCS defense reject.
- Reviewers, often practitioners, check whether the evaluation environment matches the threat model. A defense claimed for production but tested only on a toy in a lab invites the relevance question.
Attack-and-defense evaluation table
| Security claim | Matching evidence | Reject pattern avoided | |---|---|---| | Exploit is practical | End-to-end run on named target with attacker cost | "Works only in a lab against a strawman" | | Defense stops the attack | Detection/prevention rate on the original attack | "No numbers, only a design argument" | | Defense resists adaptation | Adaptive attacker with defense knowledge, degraded results | "Only the non-adaptive attack was tried" | | Deployment is feasible | Overhead, memory, compatibility on a realistic workload | "Security claimed, cost never measured" |
Vignette: evaluating a control-flow-integrity defense
Suppose the paper proposes a fine-grained CFI scheme. The matching plan: reproduce a known code-reuse attack and show it blocked; construct an adaptive attacker that respects the CFI policy and search for surviving gadget chains; then measure runtime overhead and binary-size growth on a standard benchmark suite. Every claim ties to a numbered table, and the adaptive result is reported even when it dents the headline.
Reporting floor
- Name every target's exact version and configuration; "a popular browser" is not a target.
- Report the attacker's resource budget (queries, time, samples) and the defense's measured overhead rather than vague "negligible cost" language.
Output format
[Experiment readiness] strong / adequate / weak
[Claim -> evidence map] <claim: exploit run / overhead table / measurement>
[Missing security evidence] <adaptive attack / baseline / cost / validation>
[Threat-model mismatch] <where the setup breaks the stated model>
[Decision-critical next run] <one experiment>
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
