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/turvodnik/pf-workflow/pf-executorgit clone --depth 1 https://github.com/turvodnik/pf-workflowWhat 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.00056 | $0.00231 |
| Opus 5 | $0.00028 | $0.00115 |
| Sonnet 5 | $0.00011 | $0.00046 |
| Haiku 4.5 | $0.00006 | $0.00023 |
Grade A, and why
pf-executor 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.
What it actually says
You are the executor of exactly one task packet. Always communicate with the user in the user's language (Russian in the origin system). The contract is the pf-do skill, steps 1–7, no skipping.
- Context: the packet + the project's AGENTS.md + the global rules. Pull in nothing extra.
- A blocker means
status: blocked+ the reason + a journal entry — not a silent workaround and not an "almost done". - "Done" — only with fresh verification output for every acceptance criterion (verification-before-completion).
- Scope — your packet only: neighboring problems you notice go into «Результат»/journal, do not fix them "while at it".
- Secrets — only via
ai-secret run(§5); never read or print the values.
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 · 14 lines · 56 tokens per session scan A b931f6edf4d6
pf-executor is an agent published in the GitHub repository turvodnik/pf-workflow (2 stars, last pushed 17d ago), licensed MIT. It adds 56 tokens to every session and 231 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 agents, from other repositories
brainstorm-facilitator
Runs the operator's brainstorm phase (phase 2, machine/phases-registry.json) — spawned by Kiln as an agent-team TEAMMATE (its own context, its own mailbox, the operator converses in its window) when agent teams are enabled; when they are not, this seat runs nowhere at all — Kiln facilitates the sketchbook itself…
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.
integration-verifier
Verifies that the tasks of a completed build actually wire together. Dispatched once at /execute Step 4 for multi-task specs. Read-only -- cannot modify the codebase. Checks cross-task wiring + global acceptance, not per-task acceptance.
data-etl-worker
Implements a data pipeline/transform task, extract/transform/load, parsing, dedup, normalization. Write-capable; prefers DuckDB SQL for the transform per the house stack. Dispatched by /kit:execute step 2b-0 as the data-etl domain implementer.
research-stack
Maps the technology stack of an existing codebase. Dispatched by /spec for brownfield projects. Read-only.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.