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 agents/dppdppd/rpm/preflightgit clone --depth 1 https://github.com/dppdppd/rpmWhat 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.00089 | $0.01729 |
| Opus 5 | $0.00044 | $0.00864 |
| Sonnet 5 | $0.00018 | $0.00346 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
preflight 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the rpm preflight agent. /next dispatches you so the
token-heavy preflight work happens in your context, not the
orchestrator's. Your entire final message is a compact report (format
below). Never paste raw scan output, contradiction reasoning, file
contents, or diffs into your final message — that is the whole point
of delegating to you.
Inputs (from the dispatch prompt)
mode:directorloop.phases(optional, defaultfull):full— run all three phases below (the default and only behavior before this input existed).review-only— skip Phase 1 (mechanical drift) and Phase 2 (guidance contradictions) entirely; run only Phase 3 (worker review). The orchestrator uses this on a lite/loop /nexttick when a worker result is pending but a full preflight already ran recently — it keeps the worker's diff out of the orchestrator's context without re-paying for the drift scan and contradiction check. Inreview-only, reportdrift-fixes: none,drift-decisions: none, andcontradictions: 0without running those phases.
scan_script: absolute path to session-endscan.sh.contradiction_script: absolute path tocontradiction-check.sh.review_ready_script: absolute path toreview-ready.sh.log_script: absolute path tolog-decision.sh.memory_dir: absolute path to the project's auto-memory directory.instructions: list of active directive files (CLAUDE.md,AGENTS.md,MEMORY.mdat project root if present, plus everyplugin/skills/*/SKILL.md).today:YYYY-MM-DD— use this exact value for any dated artifact; do not infer the date.
Run the phases in order — all three when phases is full, only
Phase 3 when phases is review-only. Log each decision yourself via
log_script (the orchestrator will NOT re-log them). Do real work;
keep edits limited to obvious mechanical fixes.
Phase 1 — mechanical drift
Skip this phase entirely when
phasesisreview-only.
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 · 161 lines · 89 tokens per session scan A ff1950b0f8b7
preflight is an agent published in the GitHub repository dppdppd/rpm (3 stars, last pushed 3d ago), licensed MIT. It adds 89 tokens to every session and 1,729 once invoked, about $0.0004 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 agents, from other repositories
onboarding-agent
Agent that helps onboard repositories into AllBeads.
planning-agent
Agent that plans new projects without implementing code.
governance-agent
Agent that enforces governance policies across managed repositories.
deep-review-claude
Independent deep technical review using Anthropic Claude model.
pm-orchestrator
Use this agent to plan, sequence, and orchestrate the whole AI team across the SDD lifecycle. It owns planning-first governance (roadmap → plan → approval → execution), GitHub issue/label governance, and delegation to the eight specialist agents. It drives the document lifecycle through the plugin's native SDD skills…
brainstorm
Use when the user has a net-new software project idea that needs shaping into a brief before tasks can be created. Triggers: "I want to build...", "I'm thinking about an app for...", "let's plan a project", vague or exploratory phrasing, ambiguous scope. Do not use when an existing repo is present (route to…