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 skills/gsaranti/pantheon/iris-syncnpx skills add gsaranti/pantheon --skill iris-syncgit clone --depth 1 https://github.com/gsaranti/pantheonWhat 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.00057 | $0.00353 |
| Opus 5 | $0.00028 | $0.00177 |
| Sonnet 5 | $0.00011 | $0.00071 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
iris-sync 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 2d 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.
What it actually says
Iris Sync
You are reading a record of a conversation between a user and Codex (a different AI coding assistant). Your job is to help the user's main Claude Code session understand what's been happening on the Codex side.
Codex chat log
!cat "${CLAUDE_PROJECT_DIR}/iris-codex-chat.md" 2>/dev/null || echo "[iris-codex-chat.md not found — Codex hasn't written any chat history to this project yet, or the Iris plugin isn't installed on the Codex side.]"
Your task
Read the chat log above and produce a brief synthesis covering:
- What they're working on. The current task, feature, or problem in one sentence.
- Recent progress. What has Codex done or attempted in the last few turns.
- Open threads. Anything unresolved, blocked, or explicitly deferred.
- The user's apparent intent. Where the user seems to be heading next, if it's clear from the conversation.
Keep the entire summary to 2–4 sentences. Do not quote the log verbatim. Do not speculate beyond what the log shows. If the log is empty or missing, say so plainly and stop.
Return the summary directly. The main Claude Code session will present it to the user.
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.
- 2d ago First seen · 29 lines · 57 tokens per session scan A 3d3b15309652
iris-sync is a skill published in the GitHub repository gsaranti/pantheon (3 stars, last pushed 10d ago), licensed MIT. It adds 57 tokens to every session and 353 once invoked, about $0.0003 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-31.
Other skills, from other repositories
good-skill
Use only for fixture validation of narrow skill routing. Avoid for normal repo work.
broad-skill
Always use this skill for every task and all tasks.
caveman-fixture
Always use caveman terse speech for every task.
missing-description
No description.
debug-assistant
Helps debug Python errors and exceptions.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.