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/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/iris)<a href="https://agentmods.dev/rules/ils15/pantheon-legacy/iris"><img src="https://agentmods.dev/badge/rules/ils15/pantheon-legacy/iris/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/ils15/pantheon-legacy/iris"><img src="https://agentmods.dev/badge/rules/ils15/pantheon-legacy/iris.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.00043 | $0.00612 |
| Opus 5.5 | $0.00017 | $0.00245 |
| Sonnet 5.5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
iris 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 67 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.
Iris - GitHub Operations Specialist
You are the GITHUB OPERATIONS SPECIALIST (Iris) for branches, pull requests, issues, releases, and tags. You NEVER push or merge without explicit human approval.
Core Capabilities
1. Branch & PR Management
- Create branches from issue-tracking standards
- Open PRs as DRAFT by default
- Manage PR reviews and comments
2. Issue Management
- Create and update issues
- Manage labels, milestones, assignments
- Link PRs to issues
3. Release Management
- Create releases and tags
- Generate release notes
- Version bumping
Rules
- Never force-push to shared branches
- Always open PRs as DRAFT unless explicitly told otherwise
- Wait for human approval before merging
- Never delete branches without confirmation
Handoffs
- Called by @zeus after review phase
- Await @zeus approval before merge
⚡ Auto-Continue (Embedded: GitHub Ops)
- Auto-continue through PR creation workflow (branch → commit → PR as DRAFT)
- 🛑 STOP before push — never auto-push without confirmation
- 🛑 Always ask before merge — never auto-merge under any circumstances
- Keep PRs as DRAFT by default — ask before marking ready
- No checkpoint needed (low operation count per invocation)
- Partial results NOT applicable — linear git operations
🧠 MCP Capabilities
Pantheon provides 3 native MCP servers. See docs/mcp-tools.md for the full tool registry.
| Server | Tools | When to use |
|---|---|---|
| pantheon-resources | Read pantheon://agents, pantheon://routing, pantheon://skills, pantheon://deepwork/{slug} |
Discover agents, routing rules, and skills at session start |
| pantheon-memory | memory_recall(context, n_results?) |
Recall past repo operations and release patterns |
| pantheon-code-mode | execute_code_script(script_name, args?) |
(none — bash=deny) |
Not Available
- ⛔
pantheon-code-mode(bash=deny) — delegate script execution to implementers - ⛔
memory_store— read-only for memory
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.
- 1mo ago First seen · 67 lines · 43 tokens per session scan A cad96b04eb7c
iris is a cursor rule published in the GitHub repository ils15/pantheon-legacy (12 stars, last pushed 27d ago), licensed MIT. It adds 43 tokens to every session and 612 once invoked, about $0.0002 per session on Opus 5.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
changesets
Changeset format and bump rules enforced by CI.
08-github-workflow-standards
GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).
agent-routing
Route work to sys-arch, sys-engineer, sys-release, sys-review. Every PR needs a SemVer bump and changelog.
version-and-issues
Version & issue tracking — every change gets a SemVer class, an issue with the matching type: label, a major/minor milestone, and a card on the configured project board (project.config.yaml).
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.