deal-with-security-advisory
Skill1 starsChanged 5 months agoMITView on GitHub
Handle a GitHub Security Advisory response for Workcell, including confidential fix development in a temporary private fork, human coordination on advisory-thread comments, CVE request, synchronized advisory publication, and immediate security release steps.
- Commits and pushes
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- paperclipai/paperclipedited, first seen Oct 8, 2026
- microsoft/amplifier-app-paperclipedited, first seen Jun 5, 2026
- jpoindexter/theft-kitedited, first seen May 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- paperclipai/paperclip★ 114k92% same
- jpoindexter/theft-kit★ 194% same
- microsoft/amplifier-app-paperclip★ 194% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- company-creatorSkill
- create-agent-adapterSkill
- doc-maintenanceSkill
- prcheckloopSkill
- pr-reportSkill
- release-changelog-discord-messageSkill
- release-changelogSkill
- releaseSkill
- design-guideSkill
- frontend-designSkill
- web-design-guidelinesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 11 are common, 0 are distinctive, and 3 are very specific to this project.
11
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Read the description, severity, cvss, and vulnerabilities fields.
- Very specific: line 74
Do not commit pnpm-lock.yaml — the repo has actions to manage this
- Very specific: line 75
Do not use descriptive branch names that leak the vulnerability (e.g., no fix-dns-rebinding-rce).
- Common: line 76
All work stays in the private fork until publication
- Common: line 81
Write the patch. Same content standards as any PR:
- Common: line 84
Consider the whole codebase, not just the narrow vulnerability path.
- Common: line 85
Ensure backwards compatibility for the database, or be explicit about what breaks
- Common: line 86
Make sure any UI components still look correct if the fix touches them
- Common: line 91
Verify the fix actually closes the attack vector described in the advisory.
- Common: line 92
Consider adjacent attack vectors — if DNS rebinding is the issue, are there other endpoints or modes with the same class of problem?
- Common: line 93
Do not introduce new dependencies unless absolutely necessary — new deps in a security patch raise eyebrows
- Common: line 135
If the reporter is not credited, add them:
- Common: line 221
If the CVE hasn't been assigned yet, that's normal — it can take a few hours.
- Common: line 230
All URLs to any pull requests or branches
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Security Vulnerability Response Instructions
⚠️ CRITICAL: This is a security vulnerability. Everything about this process is confidential until the advisory is published. Do not mention the vulnerability details in any public commit message, PR title, branch name, or comment. Do not push anything to a public branch. Do not discuss specifics in any public channel. Assume anything on the public repo is visible to attackers who will exploit the window between disclosure and user upgrades.
Context
A security vulnerability has been reported via GitHub Security Advisory:
- Advisory: {{ghsaId}} (e.g. GHSA-x8hx-rhr2-9rf7)
- Reporter: {{reporterHandle}}
- Severity: {{severity}}
- Notes: {{notes}}
Step 0: Fetch the Advisory Details
Pull the full advisory so you understand the vulnerability before doing anything else:
gh api repos/workcell/workcell/security-advisories/{{ghsaId}}
Read the description, severity, cvss, and vulnerabilities fields. Understand the attack vector before writing code.
Step 1: Acknowledge the Report
⚠️ This step requires a human. The advisory thread does not have a comment API. Ask the human operator to post a comment on the private advisory thread acknowledging the report. Provide them this template:
Thanks for the report, @{{reporterHandle}}. We've confirmed the issue and are working on a fix. We're targeting a patch release within {{timeframe}}. We'll keep you updated here.
Give your human this template, but still continue
Below we use gh tools - you do have access and credentials outside of your sandbox, so use them.
Step 2: Create the Temporary Private Fork
This is where all fix development happens. Never push to the public repo.
gh api --method POST \
repos/workcell/workcell/security-advisories/{{ghsaId}}/forks
This returns a repository object for the private fork. Save the full_name and clone_url.
Clone it and set up your workspace:
# Clone the private fork somewhere outside ~/workcell
git clone <clone_url_from_response> ~/security-patch-{{ghsaId}}
cd ~/security-patch-{{ghsaId}}
git checkout -b security-fix
Do not edit ~/workcell — the dev server is running off the ~/workcell master branch and we don't want to touch it. All work happens in the private fork clone.
TIPS:
- Do not commit
pnpm-lock.yaml— the repo has actions to manage this - Do not use descriptive branch names that leak the vulnerability (e.g., no
fix-dns-rebinding-rce). Use something generic likesecurity-fix - All work stays in the private fork until publication
- CI/GitHub Actions will NOT run on the temporary private fork — this is a GitHub limitation by design. You must run tests locally
Step 3: Develop and Validate the Fix
Write the patch. Same content standards as any PR:
- It must functionally work — run tests locally since CI won't run on the private fork
- Consider the whole codebase, not just the narrow vulnerability path. A patch that fixes one vector but opens another is worse than no patch
- Ensure backwards compatibility for the database, or be explicit about what breaks
- Make sure any UI components still look correct if the fix touches them
- The fix should be minimal and focused — don't bundle unrelated changes into a security patch. Reviewers (and the reporter) should be able to read the diff and understand exactly what changed and why
Specific to security fixes:
- Verify the fix actually closes the attack vector described in the advisory. Reproduce the vulnerability first (using the reporter's description), then confirm the patch prevents it
- Consider adjacent attack vectors — if DNS rebinding is the issue, are there other endpoints or modes with the same class of problem?
- Do not introduce new dependencies unless absolutely necessary — new deps in a security patch raise eyebrows
Push your fix to the private fork:
git add -A
git commit -m "Fix security vulnerability"
git push origin security-fix
Step 4: Coordinate with the Reporter
⚠️ This step requires a human. Ask the human operator to post on the advisory thread letting the reporter know the fix is ready and giving them a chance to review. Provide them this template:
@{{reporterHandle}} — fix is ready in the private fork if you'd like to review before we publish. Planning to release within {{timeframe}}.
Proceed
Step 5: Request a CVE
This makes vulnerability scanners (npm audit, Snyk, Dependabot) warn users to upgrade. Without it, nobody gets automated notification.
gh api --method POST \
repos/workcell/workcell/security-advisories/{{ghsaId}}/cve
GitHub is a CVE Numbering Authority and will assign one automatically. The CVE may take a few hours to propagate after the advisory is published.
Step 6: Publish Everything Simultaneously
This all happens at once — do not stagger these steps. The goal is zero window between the vulnerability becoming public knowledge and the fix being available.
6a. Verify reporter credit before publishing
gh api repos/workcell/workcell/security-advisories/{{ghsaId}} --jq '.credits'
If the reporter is not credited, add them:
gh api --method PATCH \
repos/workcell/workcell/security-advisories/{{ghsaId}} \
--input - << 'EOF'
{
"credits": [
{
"login": "{{reporterHandle}}",
"type": "reporter"
}
]
}
EOF
6b. Update the advisory with the patched version and publish
gh api --method PATCH \
repos/workcell/workcell/security-advisories/{{ghsaId}} \
--input - << 'EOF'
{
"state": "published",
"vulnerabilities": [
{
"package": {
"ecosystem": "npm",
"name": "workcell"
},
"vulnerable_version_range": "< {{patchedVersion}}",
"patched_versions": "{{patchedVersion}}"
}
]
}
EOF
Publishing the advisory simultaneously:
- Makes the GHSA public
- Merges the temporary private fork into your repo
- Triggers the CVE assignment (if requested in step 5)
6c. Cut a release immediately after merge
cd ~/workcell
git pull origin master
gh release create v{{patchedVersion}} \
--repo workcell/workcell \
--title "v{{patchedVersion}} — Security Release" \
--notes "## Security Release
This release fixes a critical security vulnerability.
### What was fixed
{{briefDescription}} (e.g., Remote code execution via DNS rebinding in \`local_trusted\` mode)
### Advisory
https://github.com/jugol/workcell/security/advisories/{{ghsaId}}
### Credit
Thanks to @{{reporterHandle}} for responsibly disclosing this vulnerability.
### Action required
All users running versions prior to {{patchedVersion}} should upgrade immediately."
Step 7: Post-Publication Verification
# Verify the advisory is published and CVE is assigned
gh api repos/workcell/workcell/security-advisories/{{ghsaId}} \
--jq '{state: .state, cve_id: .cve_id, published_at: .published_at}'
# Verify the release exists
gh release view v{{patchedVersion}} --repo workcell/workcell
If the CVE hasn't been assigned yet, that's normal — it can take a few hours.
⚠️ Human step: Ask the human operator to post a final comment on the advisory thread confirming publication and thanking the reporter.
Tell the human operator what you did by posting a comment to this task, including:
- The published advisory URL:
https://github.com/jugol/workcell/security/advisories/{{ghsaId}} - The release URL
- Whether the CVE has been assigned yet
- All URLs to any pull requests or branches
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

