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.
git clone --depth 1 https://github.com/dnsabby/MSITM.6341Wrote 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/rules/dnsabby/msitm.6341/master-prompt)<a href="https://agentmods.dev/rules/dnsabby/msitm.6341/master-prompt"><img src="https://agentmods.dev/badge/rules/dnsabby/msitm.6341/master-prompt/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/rules/dnsabby/msitm.6341/master-prompt"><img src="https://agentmods.dev/badge/rules/dnsabby/msitm.6341/master-prompt.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.00369 | $0.00369 |
| Opus 5.5 | $0.00148 | $0.00148 |
| Sonnet 5.5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
master-prompt 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 1mo 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
Read AGENTS.md first.
Canonical Cursor rule: ../../Master.Prompt/.cursor/rules/master-prompt.mdc
Read AGENTS.md first.
Use ../../Master.Doc/MSITM.6341/claude.md for app-specific context.
Use ../../Master.Doc/_project/dbu-msitm-6341/claude.md for project-shared runtime context.
Treat ../../Master.Prompt/ as the canonical command/workflow catalog.
Run node ../../Master.Prompt/.claude/scripts/maintenance/orchestration-preflight.js --write before governed planning, research, coding, QA, docs, or DevOps execution.
After every completed prompt or IDE command/workflow, run node ../../Master.Prompt/.claude/scripts/maintenance/shared-memory-sync.js --json --promotion-scope orchestration-alignment --project dbu-msitm-6341 --master-prompt-root ../../Master.Prompt --master-doc-root ../../Master.Doc so all IDEs keep shared-memory cache status and promotion backlog aligned.
Resolve prompt architecture updates through ../../Master.Prompt/, not machine-specific local paths.
Start with /auto-pilot unless the prompt explicitly chooses another route.
Use ../../Master.Prompt/.claude/scripts/maintenance/orchestration-preflight.js as the governed preflight entrypoint.
After every completed prompt or IDE command/workflow, run node ../../Master.Prompt/.claude/scripts/maintenance/shared-memory-sync.js --json --promotion-scope orchestration-alignment --project dbu-msitm-6341 --master-prompt-root ../../Master.Prompt --master-doc-root ../../Master.Doc so all IDEs keep shared-memory cache status and promotion backlog aligned.
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.
- 1mo ago First seen · 20 lines · 369 tokens per session scan A b6d269d02fc8
master-prompt is a cursor rule published in the GitHub repository dnsabby/MSITM.6341 (6 stars, last pushed 5mo ago), licensed MIT. It adds 369 tokens to every session, about $0.0015 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-09-04.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.