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 commands/bookedsolidtech/helixir/pm-statusgit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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.00000 | $0.02081 |
| Opus 5 | $0.00000 | $0.01040 |
| Sonnet 5 | $0.00000 | $0.00416 |
| Haiku 4.5 | $0.00000 | $0.00208 |
Grade A, and why
pm-status 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan open PRs, report pipeline state, merge ready work to dev, and keep the staging promotion PR current.
Usage
/pm-status
No arguments. The command operates on the current repo derived from gh repo view.
Step 1 — Check prerequisites
Before anything else:
- Read
.rea/policy.yaml— confirm autonomy level is L1 or higher. L0 blocks all writes; report and stop. - Check for
.rea/HALT— if the file exists, stop immediately: "Agent operations frozen. Check .rea/HALT." - Verify
ghCLI is available:gh --version - Resolve the current repo:
gh repo view --json nameWithOwner --jq '.nameWithOwner'
Store the result as {owner}/{repo} for all subsequent API calls.
Step 2 — Scan open PRs
Fetch all open PRs in a single call:
gh pr list \
--repo {owner}/{repo} \
--state open \
--json number,title,headRefName,baseRefName,statusCheckRollup,isDraft,mergeable,labels \
--limit 50
Parse the JSON array and categorize each PR into exactly one bucket:
| Bucket | Criteria |
|---|---|
| release-pending | baseRefName == "main" AND (headRefName == "changeset-release/main" OR title contains "version packages") |
| staging-promotion | baseRefName == "staging" AND headRefName == "dev" |
| ready | baseRefName == "dev" AND isDraft == false AND all entries in statusCheckRollup have state == "SUCCESS" AND statusCheckRollup is non-empty |
| blocked | baseRefName == "dev" AND isDraft == false AND any entry in statusCheckRollup has state == "FAILURE" or state == "ERROR" |
| ci-pending | baseRefName == "dev" AND isDraft == false AND any entry in statusCheckRollup has state == "PENDING" or state == "IN_PROGRESS" AND no entries are FAILURE/ERROR |
| other | anything that does not match the above |
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 · 231 lines · 0 tokens per session scan A c3cbead789b6
pm-status is a command published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,081 tokens. 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 commands, from other repositories
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
test-integration
Write integration tests for component boundaries.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.