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/Mozurok/fhorja.devWrote 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/commands/mozurok/fhorja.dev/pr-feedback-ingest)<a href="https://agentmods.dev/commands/mozurok/fhorja.dev/pr-feedback-ingest"><img src="https://agentmods.dev/badge/commands/mozurok/fhorja.dev/pr-feedback-ingest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mozurok/fhorja.dev/pr-feedback-ingest"><img src="https://agentmods.dev/badge/commands/mozurok/fhorja.dev/pr-feedback-ingest.svg" alt="Reviewed on agentmods" width="80" 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.00090 | $0.05485 |
| Opus 5.5 | $0.00036 | $0.02194 |
| Sonnet 5.5 | $0.00018 | $0.01097 |
| Haiku 4.5 | $0.00009 | $0.00549 |
Grade A, and why
pr-feedback-ingest 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 12d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-feedback-ingest
Act as a senior/staff engineer consolidating pull-request review feedback (including automated tools such as Greptile and GitHub inline comments) into task memory and an actionable correction plan aligned with the current decisions and implementation plan.
Goal:
Turn PR feedback into a structured, traceable backlog that matches TASK_STATE.md, DECISIONS.md, and IMPLEMENTATION_PLAN.md, so the next execution step can be a narrow implement-approved-slice (or a small planning touch) without losing alignment.
Mandatory context bootstrap (before any output):
- Read these sections in
WORKFLOW_OPERATING_SYSTEM.mdfirst:## LLM execution contract## Editor mode policy(mode definitions only; the tool mapping table is lazy-loaded inwos/editor-mode-mappings.mdand needed only for non-Claude-Code tools)## Global output contract(including Adaptive handoff and Mode selection rule)## Cross-cutting workflow guardrails
- Bootstrap tiers: the light-weight commands (
branch-commit,what-next,where-we-at,slice-closure,compact-task-memory) plus the high-frequencyimplement-approved-sliceandsync-task-state(v3 wave1 item D) read the four sections above with two subsections of## Cross-cutting workflow guardrailsskipped:### External web access (centralized)and### Sequencing heuristics (by phase). Everything else is read at every tier, including### Proposal vs approved persistenceand### Substrate peer ownership (per ADR-0034), since all seven write substrate sections and reason about PROPOSED (state-reconcilestays on the full tier for cross-artifact judgment). The full tier is measured at 12109 tokens, the four always-read sections combined; the two skipped subsections are 1,034 of those (measured 2026-09-28), so the reduced tier is about 11,074. The leaf-reviewer tier (verify-against-rubric, ADR-0226) reads only## Global output contract, measured at 5215 tokens, plus its rubric. - Session bootstrap reuse (skip-if-unchanged; v3 wave1 item D): WHEN this conversation already read the bootstrap sections in an earlier turn still VISIBLE in the context window AND
WORKFLOW_OPERATING_SYSTEM.mdhas not changed since, the command MAY skip the re-read and cite the earlier one, emitting one Command transcript line:Bootstrap: reusing turn <N> read, WOS unchanged. Scoped exception to the context-budget re-fetch rule (wos/context-budget.md, "The re-fetch rule"), because these sections are one large, static, byte-identical read repeated every turn; every other tool result still re-fetches. VISIBLE means the section text itself is still present and quotable now, not merely that a record of the earlier read exists: a harness that clears a tool result while the record survives (ADR-0114) has not satisfied VISIBLE, and self-declared memory after a compaction never qualifies. A stateless-per-turn harness is excluded. The transcript line is mandatory; a silent skip is invalid output. - Resolving the spec and
wos/<topic>.md: canonical repository FIRST. Otherwise use active-adapter docs:~/.claude/workflow-docs(CLAUDE_WORKFLOW_DOCS_DIR),~/.cursor/workflow-docs(WORKFLOW_DOCS_DIR; project.cursor/workflow-docson project installs),~/.codex/workflow-docs(CODEX_WORKFLOW_DOCS_DIR), or<kimi-home>/workflow-docs(KIMI_WORKFLOW_DOCS_DIR). Nonempty overrides win. Kimi home:KIMI_CODE_HOME, else existing~/.kimi-code, else existing~/.kimi, default~/.kimi-code. Use one root for both paths; try other adapters if absent or unknown. Report resolved root, fallback to other adapters, or missing mandatory context in### Command transcript. Installed snapshots refresh and prune retired topics only on sync. - Read additional sections only when relevant to this command's role.
- Align all routing recommendations and next-command suggestions with the current command set.
- Official next-command names only: recommendations, including
Run now, use registered names fromcommands/<name>.mdorcommands/<name>/SKILL.md; installed mode uses the available Fhorja command or skill inventory. No invented aliases.Run now: nonewithMode: N/Aends only if no honest next step exists, defined under### Official command names (routing integrity)(ADR-0126). Required inputs: - active task folder path
- PR identifier (the URL, the number, or both) and branch names if known
- feedback payload: Greptile summary, GitHub review comments, check annotations, or a consolidated paste
TASK_STATE.mdSOURCE_OF_TRUTH.mdDECISIONS.mdIMPLEMENTATION_PLAN.md- optional:
SLICES/*.md,TEST_STRATEGY.md,PR_PACKAGE.md,INVARIANTS_AND_NON_GOALS.md - optional:
git diff <base>...HEADor--statwhen tying comments to the diff - optional:
--playtestto ingest playtest notes (a tester's observations of a Godot build) instead of PR feedback (DECISIONS D-2, ADR-0069; off by default, corrective scope only) - optional:
--mcp-pullto pull PR review threads through a vetted, connected code-review or issue-tracker MCP instead of a pasted payload (DECISIONS D-1..D-4 of the 2026-07-03 mcp-integrations task; off by default, corrective scope 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.
- 12d ago Changed · -39 tokens per session b1fa6c9720b4
- 15d ago Changed · -1 lines 2cca433293d0
- 22d ago Changed · -1 lines f2182dd2d535
- 23d ago Changed · -2 lines · +129 tokens per session bf882cc11561
- 1mo ago First seen · 158 lines · 0 tokens per session scan A 4fff628a799c
pr-feedback-ingest is a command published in the GitHub repository Mozurok/fhorja.dev (10 stars, last pushed 12d ago), licensed MIT. It adds 90 tokens to every session and 5,485 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other commands, from other repositories
validate-impl
Validate implementation against requirements, design, and tasks.
skill-creator
Create or update an OpenCode skill using the bundled skill-creator workflow.
kiro-spec-tasks
Command "kiro-spec-tasks" from gotalab/cc-sdd, covering implementation tasks generator, core task, execution steps, step 1: load context and step 2: generate implementation tasks.
ijfw-status
Show IJFW state -- mode, routing, memory, recent activity, codebase index, settings. Use when you want the at-a-glance banner you'd otherwise get at session start.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
specmanager-board
Open the SpecManager kanban board in your default browser.