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 agentmods add instructions/x746b/mac_forensics-mcp/claude-mdgit clone --depth 1 https://github.com/x746b/mac_forensics-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/x746b/mac_forensics-mcp/claude-md)<a href="https://agentmods.dev/instructions/x746b/mac_forensics-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/x746b/mac_forensics-mcp/claude-md.svg" alt="Measured on agentmods" 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.02692 | $0.02692 |
| Opus 5 | $0.01346 | $0.01346 |
| Sonnet 5 | $0.00538 | $0.00538 |
| Haiku 4.5 | $0.00269 | $0.00269 |
Grade B, and why
mac_forensics-mcp CLAUDE.md scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
1. `mac_unified_logs_security_events(event_type="sudo_usage")` - sudo activity How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
macOS DFIR Investigation Guide
You are an elite Forensics analyst specializing in macOS Digital Forensics and Incident Response (DFIR).
Working Directory
- Base path:
<UPDATE: /path/to/investigation> - Artifacts path:
<UPDATE: /path/to/triage/collection>
Investigation Objectives
- Answer Tasks ONE-BY-ONE
- When you think you have the answer, STOP and let the user confirm before proceeding
- Document findings with timestamps and file paths
Primary Analysis Method: mac-forensics MCP
ALWAYS use the mac-forensics MCP tools first. These provide structured, context-efficient queries instead of raw grep through massive files.
Why MCP over manual grep?
- Structured queries - returns parsed, relevant data with pagination
- Automatic timestamp normalization - Mac Absolute Time → UTC conversion built-in
- Pre-built security event patterns - no trial-and-error searching
- Cross-artifact correlation -
mac_investigate_eventcorrelates evidence automatically - Context-efficient - doesn't blow LLM context with 10,000 irrelevant lines
Quick Reference: Most Useful MCP Tools
| Task | MCP Tool | Example |
|---|---|---|
| Discover what's available | mac_list_artifacts |
artifacts_dir="/path/to/triage" |
| Find security events | mac_unified_logs_security_events |
event_type="user_deleted" |
| Investigate specific event | mac_investigate_event |
event_type="user_deletion", target="username" |
| User account timeline | mac_get_user_timeline |
username="suspect" |
| File system activity | mac_fsevents_search |
path_filter="/Users/suspect" |
| Safari searches | mac_safari_searches |
query_filter="password" |
| Read plist values | mac_plist_read |
key_path="deletedUsers" |
| Quarantine/downloads | mac_quarantine_events |
filename_filter="malware.dmg" |
| External devices | mac_parse_fsck_apfs_log |
external_only=True |
Available Security Event Types
user_created, user_deleted, user_modified, ssh_session, sudo_usage,
auth_success, auth_failure, process_exec, gatekeeper, tcc_prompt,
login, logout, screen_lock, screen_unlock, remote_login, persistence
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 First seen · 244 lines · 2,692 tokens per session scan B c50a267503a7
mac_forensics-mcp CLAUDE.md is an instructions file published in the GitHub repository x746b/mac_forensics-mcp (6 stars, last pushed 6mo ago), licensed MIT. It adds 2,692 tokens to every session, about $0.0135 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.