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/genericservice/imessage-mcp-server/gemini-mdgit clone --depth 1 https://github.com/genericService/imessage-mcp-serverWrote 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/genericservice/imessage-mcp-server/gemini-md)<a href="https://agentmods.dev/instructions/genericservice/imessage-mcp-server/gemini-md"><img src="https://agentmods.dev/badge/instructions/genericservice/imessage-mcp-server/gemini-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 | $0.00533 | $0.00533 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
imessage-mcp-server GEMINI.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 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Rules: iMessage MCP Server
Pop-Culture Franchise Placeholders
- Franchise: Dune (e.g., Arrakis, Paul Atreides, Fremen, Caladan, Harkonnen, CHOAM, Spice Melange).
1. Test-Driven Development (TDD) Protocol
- Red-Green-Refactor Cycle:
- Red: Write a failing test in
tests/defining expected component or API contract behavior before modifying or adding implementation code. - Green: Write minimal implementation code necessary to satisfy test assertions.
- Refactor: Clean up implementation code while ensuring all tests continue to pass.
- Red: Write a failing test in
- Mandatory Test Verification:
- Run
pnpm test(Vitest) andpnpm build(tsc) after every code change. - Never declare a feature or refactor complete without verifying passing automated tests.
- Run
- Test Scoping:
- Unit tests for tool argument parsing, binary message parsing (
parse_attributed_body), and payload schema outputs. - Integration tests for Express routes (
/health,/discover,/mcp,/sse).
- Unit tests for tool argument parsing, binary message parsing (
2. Schema-Driven Development (SDD) Protocol
- Schema as Single Source of Truth:
- All MCP tool signatures, request payloads, and API outputs must be formally defined as explicit JSON schemas or TypeScript interfaces in
TOOLSwithin src/index.ts. - Runtime validation must strictly match published schema signatures.
- All MCP tool signatures, request payloads, and API outputs must be formally defined as explicit JSON schemas or TypeScript interfaces in
- Contract Driven API Endpoints:
/discoverendpoint output must be derived dynamically from the canonicalTOOLSarray schema to ensure documentation and runtime contracts never drift.- Any parameter change in
TOOLSmust update corresponding CLI interface specifications and unit tests.
- Input Boundary Sanitization:
- Validate all input parameters (e.g.
limit,days,chat,query,recipient,path) at entry point using strict boundary checks before executing CLI subcommands.
- Validate all input parameters (e.g.
3. General Development Standards
- Package Manager:
pnpmONLY. Usepnpm install,pnpm run,pnpm add. - Node.js Engine:
>=24.0.0(Active LTS). Enforced viapackage.json. - Imports: Absolute imports or relative ESM imports with
.jsextensions as required by NodeNext module resolution.
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 · 41 lines · 533 tokens per session scan A 7abc0cda0d85
imessage-mcp-server GEMINI.md is an instructions file published in the GitHub repository genericService/imessage-mcp-server (0 stars, last pushed 11d ago), licensed MIT. It adds 533 tokens to every session, about $0.0027 per session on Opus 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-31.
Other instructions, from other repositories
wallfacer CLAUDE.md
Instructions for changkun/wallfacer: If you didn't add a test, you didn't fix a bug. Every bug fix must include a reproducible test that fails without the fix and passes with it. You commit frequently, one small scope diff at a time. Push to main once a full batch of work is complete and verified. Leftover must be…
digital-service-orchestra skills.instructions.md
Instructions for navapbc/digital-service-orchestra, a project described as: Workflow infrastructure plugin for Claude Code projects — TDD-driven sprint management, review gates, hook parameterization, and multi-stack config.
spec-driven-tdd AGENTS.md
Instructions for strelov1/spec-driven-tdd: This repo is a skill-pack. When implementing an OpenSpec change, invoke the spec-driven-tdd skill and follow its lifecycle: plan in OpenSpec, isolate in a worktree, implement each task via TDD → simplify → review, then finish + archive.
speckit AGENTS.md
AGENTS.md instructions for jmanhype/speckit, covering agents.md - instructions for ai coding agents, core philosophy, pivotal methodology alignment, pivotal-style epic format and priority levels (pivotal-aligned).
mcp-repo-onboarding AGENTS.md
Instructions for rogermt/mcp-repo-onboarding, covering agents.md — agent & copilot instructions, current status, output verification, project identity and ⚠️ critical: tdd required.
arxiv-agent-mcp AGENTS.md
AGENTS.md instructions for tbaraniuk/arxiv-agent-mcp, covering agents.md, roles, test-writer, implementer and per-task loop.