pyro

A project-status and navigation skill for Pyro Kit, a set of project workflow tools.

In plain words
What is it for?
Use it to initialize or inspect project state, check status, list available skills, and choose the next workflow action.
Why use it?
It shows where a project is in its lifecycle and recommends a next step based on saved state and momentum.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/pyros-projects/limitless/pyro
Any agent
npx skills add pyros-projects/limitless --skill pyro
Clone the repo
git clone --depth 1 https://github.com/pyros-projects/limitless

Made for: Claude Code, Codex.

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,821 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 161692fd23d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/pyro-kit/skills/pyro/SKILL.md · 280 lines

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

Read the full file on GitHub · 280 lines

Files

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.

Changes

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.

  1. 2d ago First seen · 280 lines · 70 tokens per session scan A 161692fd23d7

Subscribe to this mod's changes

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.