fork-pov

A maintenance command for updating a project's point-of-view file or recording a specific lesson after an agent failure. It reads the project's existing taste and known-problem notes before drafting a small change.

In plain words
What is it for?
Use it to prepare a diff for an installer to adopt, or to add one actionable failure note to a gotchas file after something goes wrong.
Why use it?
It turns recurring preferences and concrete failures into maintainable guidance without overwriting project files automatically.

Command

Install

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.

agentmods
npx agentmods add commands/agentsorg/design-engineering/fork-pov
Clone the repo
git clone --depth 1 https://github.com/AgentsORG/design-engineering
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 171 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00171
Opus 5 $0.00014 $0.00086
Sonnet 5 $0.00005 $0.00034
Haiku 4.5 $0.00003 $0.00017

Measured 2d ago against content hash 33ec5eaeb917, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fork-pov 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.

commands/fork-pov.md · 16 lines

What it actually says

Fork POV

Spawn or emulate the pov-curator subagent (agents/pov-curator.md).

  1. Read skills/design-engineering/references/meta/pov.md and gotchas.md.
  2. If forking taste: produce a diff-ready pov.md the installer can adopt — short, opinionated, no generic platitudes.
  3. If logging a failure: draft one append-only line for gotchas.md — specific, actionable, not a paragraph.
  4. Never overwrite installer files without explicit user confirmation.

Read SOUL.md for voice; this command narrows it to maintenance work.

Changes

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.

  1. 2d ago First seen · 16 lines · 27 tokens per session scan A 33ec5eaeb917

Subscribe to this mod's changes

fork-pov is a command published in the GitHub repository AgentsORG/design-engineering (21 stars, last pushed 10d ago), licensed MIT. It adds 27 tokens to every session and 171 once invoked, about $0.0001 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-30.