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/thenicksanchez/passkey-mcp/agents-mdgit clone --depth 1 https://github.com/TheNickSanchez/passkey-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/thenicksanchez/passkey-mcp/agents-md)<a href="https://agentmods.dev/instructions/thenicksanchez/passkey-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/thenicksanchez/passkey-mcp/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 | $0.02282 | $0.02282 |
| Opus 5 | $0.01141 | $0.01141 |
| Sonnet 5 | $0.00456 | $0.00456 |
| Haiku 4.5 | $0.00228 | $0.00228 |
Grade B, and why
passkey-mcp AGENTS.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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
`_require_auth()` → real `sudo -v`. Without a cached sudo timestamp it How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
passkey-mcp — Agent Notes
Read this before touching anything. It documents verified reality, not
aspirations. The roadmap is PLAN.md; current version is 0.3.0 (pre-1.0 —
the old 1.x labels were re-baselined, see CHANGELOG.md).
Environment
- Python: 3.10+ floor; dev machine runs 3.14 (
uvmanages it) - Package manager:
uv— neverpip.uv synccreates.venv/ - CLI install:
pipx install --force -e .— required after any change you want to exercise through the realpasskeycommand - One-off validation without reinstall:
uv run passkey <args>oruv run python -c "from passkey.cli import main; ..."
Testing — the truth (verified 2026-07-28)
The suite does NOT pass as-committed. Do not trust any doc that says it does. There is no CI. Three independent problems:
tests/test_cli.pyhangs forever. Tests call realmain()→_require_auth()→ realsudo -v. Without a cached sudo timestamp it blocks on an interactive prompt. Nothing mocks the auth layer. (It "passes" on the maintainer's Mac only becausepam_tid.sowas hand-added to/etc/pam.d/sudoand Touch ID silently approves.)tests/test_bundle.pytakes ~2 minutes. Production scrypt is N=2^20 ≈ 5s/derivation on this machine, and the file does 20+ derivations.- Tests pollute real user state. Keyring is mocked but
audit.pyand the metadata lock are not — test runs write fake rows into the real~/Library/Application Support/passkey/audit.log(entries namedtest,found,existingare test fixtures, not your activity).
Also: pytest-timeout is NOT installed — uv run pytest --timeout=120
errors out, despite what old docs say. ruff is NOT in the synced venv
(declared under [project.optional-dependencies] dev, which uv sync
ignores in favor of [dependency-groups] dev). Use uvx ruff check instead.
How to actually validate changes today
# Fast subset — everything EXCEPT cli/bundle hangs-and-slowdowns (~0.5s, 250 tests)
uv run pytest --ignore=tests/test_cli.py --ignore=tests/test_bundle.py -q
# CLI tests: only with auth mocked or sudo cached; run per-file with care
uv run pytest tests/test_cli.py -q # HANGS without Touch ID/sudo cache
# Bundle tests: green but ~2 min
uv run pytest tests/test_bundle.py -q
# Lint (ruff is not in the venv)
uvx ruff check passkey/ tests/
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.
- 3d ago First seen · 154 lines · 2,282 tokens per session scan B 28a80e4869f1
passkey-mcp AGENTS.md is an instructions file published in the GitHub repository TheNickSanchez/passkey-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,282 tokens to every session, about $0.0114 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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.