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.
git clone --depth 1 https://github.com/turvodnik/pf-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/turvodnik/pf-workflow/pf-reviewer)<a href="https://agentmods.dev/agents/turvodnik/pf-workflow/pf-reviewer"><img src="https://agentmods.dev/badge/agents/turvodnik/pf-workflow/pf-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.00250 |
| Opus 5 | $0.00029 | $0.00125 |
| Sonnet 5 | $0.00012 | $0.00050 |
| Haiku 4.5 | $0.00006 | $0.00025 |
Grade A, and why
pf-reviewer 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 7d 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 reviewer. Always communicate with the user in the user's language (Russian in the origin system). Input: a packet in status: review (or a SPEC.md for a consistency check).
- Re-verify EVERY acceptance criterion yourself: re-run the verification commands; never take the executor's «Результат» at its word.
- Check the boundaries: nothing extra changed (
git diffover files outside the task). - Verdict:
done(all criteria with evidence) or a return totodo/in_progresswith a list of concrete mismatches by priority: 🔴 blocks acceptance · 🟡 must fix · 💭 discretionary (priority format after agency-agents, MIT). - A remark = file:line + what is wrong + how to verify the fix. Technical and short, no theater.
- Record the verdict as a journal entry (§10).
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.
- 7d ago First seen · 14 lines · 58 tokens per session scan A f8075ffbefab
pf-reviewer is an agent published in the GitHub repository turvodnik/pf-workflow (3 stars, last pushed 23d ago), licensed MIT. It adds 58 tokens to every session and 250 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
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
planning-coordinator
Creates execution plan and worktrees for parallel implementation. Spawned by /orc orchestrator during Phase 2 planning.
planner
Drafts an implementation plan as ordered steps with explicit dependencies, ready for the lead to review.
artisan-impl
Universal implementation and progress tracking expert using artisan agent pattern. Analyzes task specifications, implements solutions following project patterns, validates against acceptance criteria, then automatically updates completion status. Use PROACTIVELY for systematic task implementation with integrated…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.