findmy-cli AGENTS.md

A project instruction file for coding agents working on the findmy-cli repository. It explains the repository’s code-review process and stores project-specific working notes.

In plain words
What is it for?
Use it to run Clawpatch reviews, manage review findings, keep generated review data out of Git, and document Homebrew tap updates.
Why use it?
It gives coding agents repeatable review steps and preserves important project knowledge between sessions.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/omarshahine/findmy-cli/agents-md
Clone the repo
git clone --depth 1 https://github.com/omarshahine/findmy-cli

Made for: Codex, OpenCode.

Per session 885 This file is loaded in full into every session.
When invoked 885 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00885 $0.00885
Opus 5 $0.00443 $0.00443
Sonnet 5 $0.00177 $0.00177
Haiku 4.5 $0.00089 $0.00089

Measured 3d ago against content hash e1f3d65ba310, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

findmy-cli 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 3d 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.

AGENTS.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Clawpatch Code Review

This repo uses Clawpatch for local automated code review. Keep .clawpatch/ ignored; it is generated runtime state containing features, findings, reports, runs, and patch attempts.

Standard workflow:

clawpatch doctor
clawpatch init          # first time only
clawpatch map
clawpatch review --limit 10
clawpatch report --output .clawpatch/reports/summary.md
clawpatch show --finding <id>
clawpatch fix --finding <id>
clawpatch revalidate --finding <id>

If this repo needs hand-authored feature coverage, keep those curated definitions in tools/clawpatch/features/ and sync/copy them into .clawpatch/features/ before review. Do not commit .clawpatch/ generated state.

Imported Claude Project Memory

Durable memory promoted from ~/.claude/projects/-Users-omarshahine-GitHub-findmy-cli/memory during the AGENTS.md migration. Keep this section current when project-specific operating knowledge changes.

memory/MEMORY.md

  • Homebrew tap auto-bump — 6 formulas self-update on v* tag via per-repo workflow + HOMEBREW_TAP_TOKEN (in chezmoi)

memory/homebrew-tap-autobump.md


name: homebrew-tap-autobump description: How omarshahine/homebrew-tap formulas auto-update on release metadata: node_type: memory type: project originSessionId: be5786e9-1fd7-4b4a-9486-e20512188e64

omarshahine/homebrew-tap (cloned at ~/GitHub/homebrew-tap) holds 6 formulas, each built from the source tarball (no bottles):

  • findmy-cli (Go+Swift), aqara-cli (Python), lutron-cli (Python), apple-pim-cli (Swift), daikin-cli (Go), trakt-cli (Go)

Each source repo has .github/workflows/publish-homebrew.yml that, on every v* tag, computes the GitHub source tarball sha256 and pushes a url+sha256 bump to the tap. The workflow only updates the first app url/sha256 pair, so vendored resource blocks (Python deps in aqara/lutron, swift-argument-parser in apple-pim) are left untouched — correct, since those change independently of app version.

Read the full file on GitHub · 53 lines

Changes

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.

  1. 3d ago First seen · 53 lines · 885 tokens per session scan A e1f3d65ba310

Subscribe to this mod's changes

findmy-cli AGENTS.md is an instructions file published in the GitHub repository omarshahine/findmy-cli (53 stars, last pushed 29d ago), licensed MIT. It adds 885 tokens to every session, about $0.0044 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-30.