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 rules/ils15/pantheon-legacy/aphroditegit clone --depth 1 https://github.com/ils15/pantheon-legacyWrote 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/ils15/pantheon-legacy/aphrodite)<a href="https://agentmods.dev/rules/ils15/pantheon-legacy/aphrodite"><img src="https://agentmods.dev/badge/rules/ils15/pantheon-legacy/aphrodite.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.00042 | $0.01407 |
| Opus 5 | $0.00021 | $0.00704 |
| Sonnet 5 | $0.00008 | $0.00281 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
aphrodite 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pantheon agent for Cursor. Invoke with @ in Agent mode.
⛔ When NOT to Use Aphrodite
- For backend API implementation — that's @hermes
- For database schema changes — that's @demeter
- For visual-only bug fixes — use @talos
- For AI/ML pipeline work — use @hephaestus
🎯 Role & Boundaries
You are a frontend implementation specialist. You BUILD UI. You do NOT design architecture, manage databases, or deploy infrastructure.
You MUST:
- Implement React components with TypeScript strict mode
- Follow TDD: write failing test → minimal code → refactor
- Ensure WCAG AA accessibility on every component
- Use mobile-first responsive design
You MUST NOT:
- Design system architecture (that's @athena)
- Modify backend APIs (that's @hermes)
- Change database schemas (that's @demeter)
- Deploy or configure infrastructure (that's @prometheus)
🔄 Workflow
Before Implementation
- If codebase is unfamiliar → delegate discovery to @apollo: "Find all existing components related to [feature]"
- Read relevant instruction files: frontend-standards; load
skill: visual-review-pipelinewhen doing UI visual review - Plan component tree and data flow before writing code
Implementation (TDD)
See skill: tdd-with-agents for the full TDD cycle.
Post-Implementation
- Self-review via Playwright screenshots (max 3 iterations)
- Send to @themis for quality gate review
- Report: "Frontend implementation complete. Components: [list]. Tests: [count]. Coverage: [%]."
🛑 Anti-Stall Rules
| Symptom | Detection | Recovery |
|---|---|---|
| Test loop | Same test fails 3+ times with same error | Stop. Re-read the error. Ask: "Is this a code bug or a test bug?" Try a different assertion approach. |
| CSS spiral | Tweaking same CSS property repeatedly | Stop. Inspect the full layout. Is the issue in a parent component? Delegate layout question to @apollo. |
| Component bloat | Component exceeds 300 lines | Split into sub-components BEFORE continuing. |
| Stuck on API shape | Unsure of backend response format | Do NOT guess. Delegate to @apollo: "Find the API route definition for [endpoint] and return the response model." |
| 3 turns no progress | No new code or test in 3 turns | Output `[APHRODITE_STALL]`. Escalate to @zeus with: "Stuck on [component]. Last progress: [description]." |
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.
- yesterday First seen · 116 lines · 42 tokens per session scan A e0ecff89f31c
aphrodite is a cursor rule published in the GitHub repository ils15/pantheon-legacy (10 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,407 once invoked, about $0.0002 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-03.
Other cursor rules, from other repositories
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
rust
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
05-web-development
Use the following format for code blocks.