Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add AppliedIR/sift-mcp --skill vhir-report-writinggit clone --depth 1 https://github.com/AppliedIR/sift-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/appliedir/sift-mcp/vhir-report-writing)<a href="https://agentmods.dev/skills/appliedir/sift-mcp/vhir-report-writing"><img src="https://agentmods.dev/badge/skills/appliedir/sift-mcp/vhir-report-writing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/appliedir/sift-mcp/vhir-report-writing"><img src="https://agentmods.dev/badge/skills/appliedir/sift-mcp/vhir-report-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.00340 |
| Opus 5.5 | $0.00017 | $0.00136 |
| Sonnet 5.5 | $0.00008 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
vhir-report-writing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Report Generation (report-mcp)
Use these tools after findings are APPROVED:
generate_report(profile)— get case data + Zeltser guidance for a report type: full, executive, timeline, ioc, findings, statusset_case_metadata(field, value)— set incident metadata (type, severity, dates, scope, team) in CASE.yamlget_case_metadata()— retrieve case metadatasave_report(filename, content)— persist rendered reportlist_reports()— list saved reportslist_profiles()— show available report types
Workflow: call generate_report → follow zeltser_guidance to call Zeltser tools → write narrative sections → save_report.
report-mcp (Report Generation)
Data-driven investigation reports with profile-based formatting.
generate_report— generate report from case data (profiles: full, executive, timeline, ioc, findings, status)set_case_metadata— set report metadata (organization, classification, etc.)get_case_metadata— retrieve report metadatalist_profiles— available report profiles with descriptionssave_report— save generated report to filelist_reports— list saved reports
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 33 lines · 42 tokens per session scan A b9e4bafa80ca
vhir-report-writing is a skill published in the GitHub repository AppliedIR/sift-mcp (18 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 340 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other skills, from other repositories
performing-cloud-forensics-with-aws-cloudtrail
Perform forensic investigation of AWS environments using CloudTrail logs to reconstruct attacker activity, identify compromised credentials, and analyze API call patterns.
collecting-volatile-evidence-from-compromised-host
Collect volatile forensic evidence from a compromised system following order of volatility, preserving memory, network connections, processes, and system state before they are lost.
agent-artifact-catalog
Research, author, and validate AI agent artifact catalog entries documenting the forensic artifacts AI agents leave on endpoints - install paths, config and credential files, MCP server configs, listening ports, process trees, registry keys, and the Windows event log records that prove a tool ran. Use this skill…
collecting-volatile-evidence-from-a-suspect-host
Collects volatile evidence from a potentially compromised host in correct order of volatility: memory, network state, running processes, logged-on users, and open handles, while preserving integrity and minimizing footprint. Activates for requests to collect volatile evidence, perform live response, or capture host…
windows-event-logs-analysis
Conduct comprehensive forensic analysis of Windows Event Logs (.evtx) to trace attacker activity including lateral movement, privilege escalation, credential dumping, persistence mechanisms, and remote code execution. Use this skill during incident response, threat hunting, or post-breach forensic investigations on…
windows-prefetch-analysis
Analyze Windows prefetch files (.pf) to determine evidence of program execution. This skill details how to extract execution times, run counts, and the paths of files accessed by a program, which is critical for incident response and malware timeline reconstruction.