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/ghostwright/phantom/ritualnpx skills add ghostwright/phantom --skill ritualgit clone --depth 1 https://github.com/ghostwright/phantomWhat 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.00018 | $0.01224 |
| Opus 5 | $0.00009 | $0.00612 |
| Sonnet 5 | $0.00004 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
ritual 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ritual: latent patterns to scheduled jobs
Goal
Find recurring behaviors in the user's history that emerged naturally over time without being formalized as scheduled jobs, and propose turning them into first-class schedules. The user does not need to remember to do the thing; the agent does it for them and delivers the result where they are.
The test is "what does the user already do on a cadence that the agent could prepare for them so they do not have to start from scratch each time." Not "what should the user be doing". Only what they already do.
Steps
1. Pull the last 60 days of sessions
Call mcp__phantom-reflective__phantom_list_sessions with days_back: 60, limit: 200. Note the started_at timestamp, channel, and the first user message of each session if you can see it.
Success criteria: you have a list of 50+ sessions from the last two months with timestamps.
2. Look for temporal repetition
Cluster the sessions by:
- Day of week (Monday, Tuesday, ...).
- Time of day (bucket into morning, midday, afternoon, evening).
- Channel.
- Topic, if you can infer it from the first message.
A candidate ritual is a cluster where:
- Three or more sessions happened.
- They share day of week OR time of day (ideally both).
- They share topic or channel.
- They are spaced at roughly the same cadence (weekly, biweekly, monthly).
Example candidates:
- "Every Monday morning around 8:30 in #ops you ask for a standup."
- "Every second Friday in Slack DM you ask me to prepare a weekly review."
- "Every first of the month in #finance you ask for a cost breakdown."
Success criteria: you have identified 1-5 candidate rituals.
3. Verify with memory
For each candidate ritual, call mcp__phantom-reflective__phantom_memory_search with a query matching the topic and days_back: 60. Confirm that memory also shows the same pattern.
Discard any candidate that the session pattern suggests but memory does not support. Discard any where the cadence is off (the user did it three Mondays in a row, then stopped two weeks ago).
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 · 102 lines · 18 tokens per session scan A 9d3d45d9a65b
ritual is a skill published in the GitHub repository ghostwright/phantom (1,463 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,224 once invoked, about $0.0001 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-30.
Other skills, from other repositories
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
os-eco-dep-sync
Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR. Use when checking if warren is on the newest burrow/plot/canopy/seeds/mulch/sapling.
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
warren-dogfood-pipeline
Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…
writing-skills
Use when a task reveals a recurring, multi-step capability worth saving for future sessions — writing a new Norma skill, or improving an existing self-authored one, via skillwrite.