Forensify
alexgreensh/repo-forensics
Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.
A skill your agent uses when drafting an ACM CCS rebuttal during the HotCRP author-response window, covering threat-model defenses, adaptive-attack objections, ethics and disclosure questions…
Install Ccs Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-author-response --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/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-author-response .claude/skills/ccs-author-response && 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 "ccs-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-author-response into .claude/skills/ccs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-author-response", 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/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-author-responseType 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 brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-author-response --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-author-response .agents/skills/ccs-author-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ccs-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-author-response into .agents/skills/ccs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-author-response", 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 brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-author-response --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-author-response .cursor/skills/ccs-author-response && 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 "ccs-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-author-response into .cursor/skills/ccs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-author-response", 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/brycewang-stanford/Awesome-Journal-Skills.git --path ACM-CCS-Skills/skills/ccs-author-response--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 brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-author-response --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-author-response .gemini/skills/ccs-author-response && 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 "ccs-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-author-response into .gemini/skills/ccs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-author-response", 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 brycewang-stanford/Awesome-Journal-Skills ccs-author-responseInstalls 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 brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-author-response .github/skills/ccs-author-response && 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 "ccs-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-author-response into .github/skills/ccs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-author-response", 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 brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-author-response --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-author-response .opencode/skills/ccs-author-response && 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 "ccs-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-author-response into .opencode/skills/ccs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-author-response", 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.
Facts
- Skill name
ccs-author-response- GitHub stars
- 1.2k
- Token cost
- ~949 tokens
- SKILL.md length
- 439 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting an ACM CCS rebuttal during the HotCRP author-response window, covering threat-model defenses, adaptive-attack objections, ethics and disclosure questions…
- Works in 4 steps: State the decision-critical correction… → Point to exact submitted evidence… → Explain the security consequence — why… → …
- Drafting an ACM CCS rebuttal during the HotCRP author-response window
- SKILL.md covers Triage, Drafting pattern, Adversarial reviewer pushback… and Response micro-example, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ccs Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an ACM CCS rebuttal during the HotCRP author-response window, covering threat-model defenses, adaptive-attack objections, ethics and disclosure questions, anonymity constraints, adversarial reviewer pushback patterns, and decision-focused replies aimed at the meta-reviewer.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Threat modeling. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Drafting an ACM CCS rebuttal during the HotCRP author-response window
- Covering threat-model defenses
- Adaptive-attack objections
- Ethics and disclosure questions
Example prompts
- “/ccs-author-response”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- State the decision-critical correction or concession in the first line.
- Point to exact submitted evidence (section, figure, appendix).
- Explain the security consequence — why the attack still holds, or the defense still binds.
- Offer a scoped camera-ready edit only where it clarifies without over-claiming.
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ccs Author Response loads about 949 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 439 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 439 words, ~949 tokens.
Download SKILL.mdSave it as
.claude/skills/ccs-author-response/SKILL.md (or your agent's skills folder).- name
- ccs-author-response
- description
- Use when drafting an ACM CCS rebuttal during the HotCRP author-response window, covering threat-model defenses, adaptive-attack objections, ethics and disclosure questions, anonymity constraints, adversarial reviewer pushback patterns, and decision-focused replies aimed at the meta-reviewer.
CCS Author Response
Use this after CCS reviews are released. Reopen the current HotCRP rebuttal instructions and any length or format limits before drafting, because response mechanics are set per cycle.
Triage
- Answer concerns that affect the decision: threat-model soundness, novelty, correctness, evidence quality, ethics, and disclosure. Skip cosmetic complaints unless space allows.
- Use evidence already in the submission: sections, appendices, measurement tables, and the ethics section. The rebuttal clarifies the submitted paper; it does not add a new paper.
- Keep the reply anonymous. Do not reveal institution, authorship, private URLs, or the identity of a disclosed vendor if that would deanonymize you.
- Correct factual misreadings first, then address the strongest objection to the attacker model or the adaptive evaluation.
- Do not promise experiments you cannot run before camera-ready; promise only edits that add no unsupported claim.
Drafting pattern
- State the decision-critical correction or concession in the first line.
- Point to exact submitted evidence (section, figure, appendix).
- Explain the security consequence — why the attack still holds, or the defense still binds.
- Offer a scoped camera-ready edit only where it clarifies without over-claiming.
Adversarial reviewer pushback patterns
| Pushback | What it signals | CCS-ready fix |
|---|---|---|
| "The attacker assumes too much" | The threat model looks unrealistic | Point to where the capability is justified, or scope the claim to the realistic subset and concede the rest |
| "You never tested an adaptive attacker" | The defense evaluation looks incomplete | Reference the adaptive experiment if present; if absent, concede and commit to a bounded camera-ready addition only if honestly feasible |
| "This is already a known CVE" | A prior-art gap | Distinguish root cause, scope, or impact from the CVE, with the specific technical delta |
| "The ethics of this are unaddressed" | Disclosure or harm concern | State the disclosure timeline, the harm-minimization steps, and the reasoning, quoting the ethics section |
Show full SKILL.md (136 more words)Show less
Response micro-example
Reviewer objection: the key-recovery attack assumes co-located measurement that real attackers cannot achieve. Reply skeleton:
- Concede the strongest form needs co-location; scope the practical claim to that setting.
- Point to Section 6 where a remote variant with degraded rate is already measured.
- Note the defense in Section 7 blocks both variants, so the contribution stands.
- Offer one camera-ready sentence making the co-location assumption explicit in the intro.
Rebuttal calibration
- One decision-critical point per reviewer beats an exhaustive rebuttal; CCS meta-reviewers read for whether the central threat-model or ethics objection was actually resolved.
- Never paste new experimental results the reviewers cannot verify; describe what exists and anchor it in the submission.
- Answer the ethics reviewer directly and early; an unaddressed disclosure concern outweighs resolved technical nits at decision time.
Output format
[Priority issue] <reviewer concern>
[Decision dimension] threat model / novelty / correctness / evidence / ethics
[Draft response] <CCS-ready anonymous text>
[Evidence anchor] <section / figure / appendix item>
[Forbidden content removed] <identity leaks, unverifiable new results, over-promises>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ACM-CCS-Skills/skills/ccs-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ccs Author Response 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 |
|---|---|---|---|---|---|---|
| Ccs Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~949 | Automated safety check: Pass | MIT | |
| Forensifyalexgreensh/repo-forensics | 190 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| Create Rulecartography-cncf/cartography | 4.1k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Commit Security Scancodexstar69/bug-hunter | 520 | — | ~629 | Automated safety check: Pass | MIT | |
| Auditing Code For Vulnerabilitiestrilwu/secskills | 157 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Threat Mitigation Mappingwshobson/agents | 40k | 8 repos | ~742 | Automated safety check: Pass | MIT |
Similar skills
Create Rule
cartography-cncf/cartography
Author a Cartography security rule (one or more Cypher Facts plus a Pydantic Finding output model) under cartography/rules/data/rules/.
Commit Security Scan
codexstar69/bug-hunter
Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context.
Auditing Code For Vulnerabilities
trilwu/secskills
Audit source code for exploitable vulnerabilities using threat-model-driven review, taint tracing, invariant checking, and variant analysis.
Threat Mitigation Mapping
wshobson/agents
Match identified threats to preventive, detective and corrective controls across network, application, data, endpoint and process layers to plan remediation.
Audit Browser Security Boundaries
nordstjernen-web/northstar-browser
Audit browser-engine changes that process untrusted content or cross native-memory, origin, network, storage, extension, decoder, sandbox, or operating-system boundaries.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Ccs Author Response
What does Ccs Author Response do?
A skill your agent uses when drafting an ACM CCS rebuttal during the HotCRP author-response window, covering threat-model defenses, adaptive-attack objections, ethics and disclosure questions…. Ccs Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an ACM CCS rebuttal during the HotCRP author-response window, covering threat-model defenses, adaptive-attack objections, ethics and disclosure questions, anonymity constraints, adversarial reviewer pushback patterns, and decision-focused replies aimed at the meta-reviewer.
When should I use Ccs Author Response?
Ccs Author Response fits situations like: drafting an ACM CCS rebuttal during the HotCRP author-response window; covering threat-model defenses; adaptive-attack objections; ethics and disclosure questions.
How do I install Ccs Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a claude-code`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ccs-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Ccs Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a codex`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ccs-author-response in your project. Codex loads it when a task matches its description.
Can I use Ccs Author Response in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-author-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccs-author-response, .gemini/skills/ccs-author-response, .github/skills/ccs-author-response and .opencode/skills/ccs-author-response in your project.
What does Ccs Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Ccs Author Response is instructions for the agent only.
Does Ccs Author Response access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ccs Author Response safe to install?
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.
What licence does Ccs Author Response use?
Ccs Author Response is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ccs Author Response use?
About 949 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ccs Author Response?
Skills that share tags, products or a category with Ccs Author Response: Forensify (alexgreensh/repo-forensics, 190 stars), Create Rule (cartography-cncf/cartography, 4.1k stars), Commit Security Scan (codexstar69/bug-hunter, 520 stars) and Auditing Code For Vulnerabilities (trilwu/secskills, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ccs Author Response?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.