A window into
the Agentic Web.
Enter a W3BS URI, a Moshpit name like chovy.hacker, a pit.world URL or any https URL. Moshpit names resolve on the server over Moshpit DNS.
Analyze incident
Extract info from breach articles, including attack details and impact.
w3bs://prompt/fabric/analyze-incident@1.0.0Instructions
Cybersecurity Hack Article Analysis: Efficient Data Extraction
Objective: To swiftly and effectively gather essential information from articles about cybersecurity breaches, prioritizing conciseness and order.
Instructions:
For each article, extract the specified information below, presenting it in an organized and succinct format. Ensure to directly utilize the article's content without making inferential conclusions.
- Attack Date: YYYY-MM-DD
- Summary: A concise overview in one sentence.
- Key Details:
- Attack Type: Main method used (e.g., "Ransomware").
- Vulnerable Component: The exploited element (e.g., "Email system").
- Attacker Information:
- Name/Organization: When available (e.g., "APT28").
- Country of Origin: If identified (e.g., "China").
- Target Information:
- Name: The targeted entity.
- Country: Location of impact (e.g., "USA").
- Size: Entity size (e.g., "Large enterprise").
- Industry: Affected sector (e.g., "Healthcare").
- Incident Details:
- CVE's: Identified CVEs (e.g., CVE-XXX, CVE-XXX).
- Accounts Compromised: Quantity (e.g., "5000").
- Business Impact: Brief description (e.g., "Operational disruption").
- Impact Explanation: In one sentence.
- Root Cause: Principal reason (e.g., "Unpatched software").
- Analysis & Recommendations:
- MITRE ATT&CK Analysis: Applicable tactics/techniques (e.g., "T1566, T1486").
- Atomic Red Team Atomics: Recommended tests (e.g., "T1566.001").
- Remediation:
- Recommendation: Summary of action (e.g., "Implement MFA").
- Action Plan: Stepwise approach (e.g., "1. Update software, 2. Train staff").
- Lessons Learned: Brief insights gained that could prevent future incidents.
# INPUT
INPUT:
{{input}}Try the template
Fill the declared inputs to render these instructions. This runtime does not call a model or any tools.
Canonical manifest
{
"specVersion": "W3BS-MANIFEST-1-draft-1",
"id": "w3bs://prompt/fabric/analyze-incident@1.0.0",
"type": "prompt",
"version": "1.0.0",
"name": "Analyze incident",
"description": "Extract info from breach articles, including attack details and impact.",
"publisher": {
"namespace": "fabric",
"name": "Fabric patterns by Daniel Miessler and contributors, imported by W3BS",
"keyId": "w3bs-fabric-1"
},
"license": "MIT",
"createdAt": "2026-10-19T00:00:00.000Z",
"provenance": {
"source": "https://github.com/danielmiessler/Fabric/blob/0018f793d746344c12aa9f1585fc3bff4faddf3f/data/patterns/analyze_incident/system.md",
"derivedFrom": []
},
"trust": {
"classification": "AGENT_INSTRUCTION"
},
"permissions": [],
"dependencies": [],
"locations": {
"canonical": "https://prompt.w3bs.org/api/manifest?uri=w3bs%3A%2F%2Fprompt%2Ffabric%2Fanalyze-incident%401.0.0",
"mirrors": []
},
"content": {
"mediaType": "text/plain",
"instructions": "\nCybersecurity Hack Article Analysis: Efficient Data Extraction\n\nObjective: To swiftly and effectively gather essential information from articles about cybersecurity breaches, prioritizing conciseness and order.\n\nInstructions:\nFor each article, extract the specified information below, presenting it in an organized and succinct format. Ensure to directly utilize the article's content without making inferential conclusions.\n\n- Attack Date: YYYY-MM-DD\n- Summary: A concise overview in one sentence.\n- Key Details:\n - Attack Type: Main method used (e.g., \"Ransomware\").\n - Vulnerable Component: The exploited element (e.g., \"Email system\").\n - Attacker Information: \n - Name/Organization: When available (e.g., \"APT28\").\n - Country of Origin: If identified (e.g., \"China\").\n - Target Information:\n - Name: The targeted entity.\n - Country: Location of impact (e.g., \"USA\").\n - Size: Entity size (e.g., \"Large enterprise\").\n - Industry: Affected sector (e.g., \"Healthcare\").\n - Incident Details:\n - CVE's: Identified CVEs (e.g., CVE-XXX, CVE-XXX).\n - Accounts Compromised: Quantity (e.g., \"5000\").\n - Business Impact: Brief description (e.g., \"Operational disruption\").\n - Impact Explanation: In one sentence.\n - Root Cause: Principal reason (e.g., \"Unpatched software\").\n- Analysis & Recommendations:\n - MITRE ATT&CK Analysis: Applicable tactics/techniques (e.g., \"T1566, T1486\").\n - Atomic Red Team Atomics: Recommended tests (e.g., \"T1566.001\").\n - Remediation:\n - Recommendation: Summary of action (e.g., \"Implement MFA\").\n - Action Plan: Stepwise approach (e.g., \"1. Update software, 2. Train staff\").\n - Lessons Learned: Brief insights gained that could prevent future incidents.\n\n# INPUT\n\nINPUT:\n\n{{input}}",
"inputs": {
"input": {
"description": "The text to run the pattern on.",
"required": true
}
},
"output": {
"mediaType": "text/plain",
"description": "Rendered instructions, ready for an explicitly authorized runtime or human review."
},
"runtime": "w3bs-template-v1",
"compatibleModels": [
"model-independent"
],
"tools": [],
"mcpServers": [],
"evaluations": [
{
"id": "template-inputs-1",
"description": "Required inputs are checked, substituted once, and cannot invoke tools."
}
]
},
"proof": {
"type": "Ed25519",
"keyId": "w3bs-fabric-1",
"digest": "sha256:bafd79f1bd82be74a87bc4e083125491fc44a8260517b0cf3bfdd757f84fcf07",
"signature": "k2KG8f7MjPqi8eUULIzx1pMHsApjInmzGAQ-WLd7qU0Mb3Ws_dqabu5EUPdCl8N0FXnd_r6nSH94jIFu-G8_DQ"
}
}Try one of ours.
Moshpit names open as themselves when your resolver speaks Moshpit, and through their pit.world gateway when it does not.
Moshpit names
chovy.hacker
A personal Moshpit name, served from a Profullstack box.
chovy.hacker.pit.worldpay.agent
Get paid in crypto with one link, on CoinPay.
pay.agent.pit.worldbuilt.indie
Launch an indie product with one URL.
built.indie.pit.worldseo.rank
A free on-page SEO audit.
seo.rank.pit.worldlive.streaming
Live stations, streaming now.
live.streaming.pit.worldfamily.ancestry
Public family trees of people, animals and companies.
family.ancestry.pit.worldsearch.peptides
Every research peptide vendor, compared.
search.peptides.pit.worldprofullstack.agent
Profullstack's agent namespace on Moshpit.
profullstack.agent.pit.worlddemo.indie
A site served from a Moshpit server.
demo.indie.pit.worldOn the Web
w3bs.org
This site: Fleet, packages and the W3BS drafts.
https://w3bs.orgprofullstack.com
Agentic engineering: the studio behind the network.
https://profullstack.comhqtui.com
Terminal UIs for TypeScript, Rust, Go, Python and Zig.
https://hqtui.comthreatcrush.com
A security agent for Linux servers; it scans W3BS packages.
https://threatcrush.comcrawlproof.com
See your site the way AI crawlers do.
https://crawlproof.comcoinpayportal.com
Crypto payments, escrow and wallets.
https://coinpayportal.commoshcode.sh
moshcode, and the Moshpit registry and resolver.
https://moshcode.shpit.world
Private search, and the gateway to every Moshpit name.
https://pit.worldad.network
Run ads or earn from your site, in crypto.
https://ad.networkThe same, on the command line.
No w3bs yet? curl -fsSL https://w3bs.org/install.sh | sh
w3bs resolve w3bs://prompt/w3bs/research@1Resolve, verify and print a signed W3BS resourcew3bs install hqtui.com/hqtui-demo-rustInstall a package from the signed repositoryw3bs packagesThe package catalog, as on w3bs.org/packagesw3bs publish key add example.comRegister your SSH key for a domain you publish underw3bs open https://w3bs.org/i/hqtui.com/hqtui-demo-rustInstall from an install link (always asks first)curl -s https://w3bs.org/.well-known/w3bs.jsonThe W3BS discovery documentdig +https @dns.moshcode.sh chovy.hacker TXT +shortLook up a Moshpit name over DNS over HTTPScurl -s 'https://pit.moshcode.sh/api/moshpit/resolve?name=chovy.hacker'Ask the Moshpit registry where a name pointscurl -s 'https://w3bs.org/api/browse?q=chovy.hacker'This page as JSON, for agents (also the w3bs_browse MCP tool)