Borrowing it
Nothing to install: this file belongs to yinanli1917-cloud/searching-apple-notes. 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/yinanli1917-cloud/searching-apple-notes/main/AGENTS.mdgit clone --depth 1 https://github.com/yinanli1917-cloud/searching-apple-notesWrote 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/yinanli1917-cloud/searching-apple-notes/agents-md)<a href="https://agentmods.dev/instructions/yinanli1917-cloud/searching-apple-notes/agents-md"><img src="https://agentmods.dev/badge/instructions/yinanli1917-cloud/searching-apple-notes/agents-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.00473 | $0.00473 |
| Opus 5 | $0.00236 | $0.00236 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
searching-apple-notes 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 8d 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
Codex Project Instructions
Migrated from Claude Code /Users/yinanli/Documents/apple-notes-mcp/CLAUDE.md on 2026-05-03. The source CLAUDE.md was left unchanged.
Codex should follow these instructions when working in this project. Claude-specific commands, hooks, and permission syntax should be interpreted as intent and adapted to Codex tools.
apple-notes-mcp
MCP server for searching, retrieving, and creating Apple Notes.
Tech Stack
- Python 3 (MCP server)
- AppleScript (Notes.app integration)
- SQLite (Apple Notes database access)
Directory Structure
| Path | Purpose |
|---|---|
scripts/ |
MCP server and utility scripts |
archive/ |
Previous versions |
Conventions
- MCP tool responses must be JSON-serializable
- Note search uses FTS (full-text search) on Apple Notes SQLite DB
- Never modify Notes.app database directly — use AppleScript for writes
Active Codex Harness
The active harness contract is .codex/workflow.md, .codex/tasks/, .codex/spec/, .codex/agents/, and scripts/codex_harness.py. Older Claude-era or .agents/harness material is legacy evidence only unless a current .codex task explicitly references it.
Before substantial work, run python3 scripts/codex_harness.py context. Before completion, run python3 scripts/codex_harness.py health plus task-specific checks, or use python3 scripts/codex_harness.py finish-work.
Codex Harness
Codex does not receive Claude hook injections automatically. Treat .codex/workflow.md and scripts/codex_harness.py context as the native pull-based context layer.
Common commands:
python3 scripts/codex_harness.py context
python3 scripts/codex_harness.py health
python3 scripts/codex_harness.py task create "<title>"
python3 scripts/codex_harness.py task start <slug-or-dir>
python3 scripts/codex_harness.py task finish [slug-or-dir]
python3 scripts/codex_harness.py task archive <slug-or-dir>
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.
- 8d ago First seen · 49 lines · 473 tokens per session scan A 5e3ffbae2475
searching-apple-notes AGENTS.md is an instructions file published in the GitHub repository yinanli1917-cloud/searching-apple-notes (2 stars, last pushed 1mo ago), licensed MIT. It adds 473 tokens to every session, about $0.0024 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
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.
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 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).
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).
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.
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.