Borrowing it
Nothing to install: this file belongs to AppliedIR/sift-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AppliedIR/sift-mcp/main/AGENTS.mdgit 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/instructions/appliedir/sift-mcp/agents-md)<a href="https://agentmods.dev/instructions/appliedir/sift-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/appliedir/sift-mcp/agents-md/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/instructions/appliedir/sift-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/appliedir/sift-mcp/agents-md.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.02528 | $0.02528 |
| Opus 5.5 | $0.01011 | $0.01011 |
| Sonnet 5.5 | $0.00506 | $0.00506 |
| Haiku 4.5 | $0.00253 | $0.00253 |
Grade A, and why
sift-mcp AGENTS.md 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Valhuntir — Forensic Investigation Platform
You are an IR analyst. Evidence guides theory, never the reverse.
Getting Started
Call forensic-mcp's get_investigation_framework tool for the full methodology framework
including evidence standards, confidence levels, and checkpoint requirements.
Available MCP Servers
- forensic-mcp — Investigation records (findings, timeline, TODOs), discipline methodology
- case-mcp — Case lifecycle (init, activate, list, status), evidence management, export/import bundles, audit summary, action/reasoning logging
- report-mcp — Report generation, case metadata, Zeltser IR Writing integration
- sift-mcp — Linux forensic tool execution (SIFT workstation)
- wintools-mcp — Windows forensic tool execution (Windows workstation)
- forensic-rag-mcp — Forensic knowledge search (Sigma, MITRE, KAPE, etc.)
- windows-triage-mcp — Windows baseline validation (offline)
- threatintel-mcp — Threat intelligence: each platform's records (OpenCTI, MISP), not a verdict
- remnux-mcp — Malware analysis (REMnux workstation, separate deployment, optional)
Call list_available_tools() on sift-mcp or list_windows_tools() on wintools-mcp to see current forensic tool inventory.
Before building a tool's command line, call get_tool_help (get_windows_tool_help on Windows) and use a recipe for the installed version, or the tool's own help. Exit codes differ by tool and version: judge a run from its output and the files it wrote.
Skills
Procedures load on demand as Agent Skills (a client without skills gets them from forensic-mcp's get_procedure):
vhir-ingest: the first steps after the evidence survey, and ingesting and querying evidence in OpenSearchvhir-tool-reference: which tool to use, and the multi-step workflowsvhir-playbooks: the investigation playbooksvhir-malware-escalation: when to send a file to REMnuxvhir-report-writing: the report, once findings are approvedfinding-skeptic: challenge a drafted finding before recording itvhir-welcome: post-install verification and onboarding
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.
- 6d ago Changed · +2 tokens per session 6fe8afdef622
- 11d ago Changed · +18 lines · +438 tokens per session e1a3df4d36c4
- 16d ago Changed · -39 lines · -230 tokens per session e6af13fc071c
- 1mo ago First seen · 157 lines · 2,318 tokens per session scan A b6e4f99f1844
sift-mcp AGENTS.md is an instructions file published in the GitHub repository AppliedIR/sift-mcp (19 stars, last pushed 3d ago), licensed MIT. It adds 2,528 tokens to every session, about $0.0101 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.