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/pyros-projects/limitless/pyronpx skills add pyros-projects/limitless --skill pyrogit clone --depth 1 https://github.com/pyros-projects/limitlessWhat 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.00070 | $0.02821 |
| Opus 5 | $0.00035 | $0.01411 |
| Sonnet 5 | $0.00014 | $0.00564 |
| Haiku 4.5 | $0.00007 | $0.00282 |
Grade A, and why
pyro 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.
How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!if [ -f .pyro/state.md ]; then cat .pyro/state.md; else echo "NO_PROJECT_STATE"; fi
Persona
Act as a lifecycle navigator for Pyro Kit. You read project state and recommend the next skill to invoke. You always lead with a concrete recommendation, never a question.
Command: $ARGUMENTS
Interface
fn init() // Initialize .pyro/ via pyro-init.sh
fn status() // Show current phase, momentum, last activity
fn list() // Display all skills by phase
fn route() // Recommend next skill based on state
Constraints
Constraints { require { Read .pyro/state.md before any recommendation. First output is ALWAYS a concrete recommendation with reasoning. Prioritize /pulse when momentum signals are negative. Show available skills with current phase highlighted in /pyro list. Handle missing state gracefully — suggest init, not error. } never { Ask open-ended questions ("what do you want to do?") Recommend skills that don't exist yet without noting they're planned. Skip momentum check — always evaluate before routing. Block on missing gates — warn but don't prevent (soft gating). } }
State
State { args = $ARGUMENTS projectState: String // contents of .pyro/state.md (or NO_PROJECT_STATE) registry: String // ~/.pyro/project-registry.yaml config: String // ~/.pyro/config.yaml phase: Number // extracted from state frontmatter momentum: String // steady | rising | declining | stalled | composted lastSkill: String // last skill invoked lastActivity: String // date of last activity soul: String // project soul statement dormancyThreshold: Number // from config, default 5 days }
Reference Materials
See reference/ directory for the full lifecycle:
- Skill Catalog — All skills grouped by phase with availability
- Phase Map — The 7-phase creative lifecycle
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 280 lines · 70 tokens per session scan A 161692fd23d7
pyro is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 20d ago), licensed MIT. It adds 70 tokens to every session and 2,821 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
omh-agent-board
This is a Hermes-native agent-board workflow skill.
omh-feedback-triage
This is a Hermes-native feedback-triage workflow skill.
triage-sweep
Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by…
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
meeting-minutes
Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…
pneuma-project
Project-context awareness — multi-session workflows around one topic, shared materials and preferences, and cross-mode handoffs as a high-value user path.