Works with the AI Agents you already use
Vulnerability Disclosure Kit: security.txt, Disclosure Policy, SECURITY.md and Triage
Set up a complete coordinated vulnerability disclosure channel: valid RFC 9116 security.txt, public policy with safe harbour, SECURITY.md and a triage runbook with deadlines.
$3
Vulnerability Disclosure Kit: security.txt, Disclosure Policy, SECURITY.md and Triage
Example session with this skill installed
We run a Laravel SaaS at app.acme.example plus a mobile app sold in the EU and UK. Reports currently arrive at random support inboxes. Set up a proper vulnerability disclosure process.
- Read your context and instructions
- Compiled the vulnerability disclosure kit
A summary table of covered origins and open questions; a security.txt (Contact, Expires, Policy, Canonical, Preferred-Languages) that passes the offline checker; a published disclosure policy with scope, safe harbour and 3-day acknowledgement target; SECURITY.md for each repo; a triage runbook with severity matrix and reply templates; a Laravel route and Nginx snippet to serve the file; and CRA/PSTI notes flagging that the mobile app is in CRA scope with 24h/72h reporting since 11 September 2026.
Connects securely to your tools. The creator never sees your data.
About this skill
Most security reports are lost not because the bug is hard but because the reporter cannot find who to tell, or the report lands in an unwatched inbox. This skill builds the complete public-facing and internal side of coordinated vulnerability disclosure (CVD) for a website, SaaS, app, device or open-source project.
What you get
- A valid RFC 9116
security.txtfor each domain, built from the current IANA field registry (including CSAF and Bug-Bounty), plus an offline, standard-library Python checker you can run in CI to catch missing fields and expiring files. - A plain-language disclosure policy template: scope, how to report, response targets, rules for researchers, safe-harbour wording and disclosure timeline.
- A
SECURITY.mdtemplate and steps to enable private vulnerability reporting on GitHub. - A triage runbook: workflow, severity matrix, closing decision table, reply templates and a public advisory format.
- Deployment snippets for Nginx, Apache, Laravel and static hosts, with a verification checklist.
- A regulatory map: EU Cyber Resilience Act reporting (24-hour early warning, 72-hour notification, final report) in force since 11 September 2026, Annex I vulnerability-handling duties from 11 December 2027, UK PSTI, and ISO/IEC 29147 / 30111 as the worldwide baseline — with official sources.
Regulatory notes are a planning summary, not legal advice.
Does not test or scan your systems for vulnerabilities, does not run a bug bounty platform, and does not file regulatory reports for you. Regulatory notes are a planning summary as of October 2026, not legal advice; have safe-harbour wording reviewed by your own adviser.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 17 days ago
Permissions
File Scopes
The bundled script is standard-library Python and makes no network requests.