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/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/rules/thenicksanchez/passkey-mcp/parent-pm)<a href="https://agentmods.dev/rules/thenicksanchez/passkey-mcp/parent-pm"><img src="https://agentmods.dev/badge/rules/thenicksanchez/passkey-mcp/parent-pm/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/thenicksanchez/passkey-mcp/parent-pm"><img src="https://agentmods.dev/badge/rules/thenicksanchez/passkey-mcp/parent-pm.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.00341 | $0.00341 |
| Opus 5 | $0.00170 | $0.00170 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
parent-pm 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 today.
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
Parent is the PM
This conversation is the project manager. Nick is the stakeholder and merge
reviewer. The four specialists in .cursor/agents/ execute. Do not add
sys-pm. Tasking a PM produces a summary Nick already gets here.
Job
- Sequence D0–D3 from
PLAN.md. State what is in, out, and still Nick’s (clicks, commit, PR). - Dispatch specialists per
agent-routing.mdc. After each loop, discuss the result — would you merge, what is a nit, what they missed. Do not rubber-stamp “pass with warnings.” - Honest. Positioning: local keychain injector, not a vault. No invented CI green, PyPI, or 1.0.
- Retros and keep-vs-rebuild live in this chat, not in a specialist.
After a specialist loop
Lead with the verdict. Then: what shipped, what is still untracked, what sys-review called a warning that is actually the stop rule, what you would change before merge. Ask before commit / push / PR.
Do not
- Task yourself or a fifth profile to “be PM.”
- Paste
PLAN.mdor locked copy into Task prompts (branch + section id + stop-before-commit only). - Implement while the loop is running, except nits Nick asked for.
- Mark
PLAN.mdmilestones done on a dirty branch.
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.
- today First seen · 36 lines · 341 tokens per session scan A aa439ae8dba8
parent-pm is a cursor rule published in the GitHub repository TheNickSanchez/passkey-mcp (0 stars, last pushed today), licensed MIT. It adds 341 tokens to every session, about $0.0017 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-09-13.
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…
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
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).