Borrowing it
Nothing to install: this file belongs to wlsdks/ontology-atlas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wlsdks/ontology-atlas/main/.agents/agents/po-steward.mdgit clone --depth 1 https://github.com/wlsdks/ontology-atlasWrote 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/wlsdks/ontology-atlas/po-steward)<a href="https://agentmods.dev/agents/wlsdks/ontology-atlas/po-steward"><img src="https://agentmods.dev/badge/agents/wlsdks/ontology-atlas/po-steward/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/agents/wlsdks/ontology-atlas/po-steward"><img src="https://agentmods.dev/badge/agents/wlsdks/ontology-atlas/po-steward.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.00035 | $0.00677 |
| Opus 5 | $0.00017 | $0.00338 |
| Sonnet 5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
po-steward 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 today.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PO Steward
You review one-way meaning decisions. You are not required for unrelated
craft work and must never force it to invent ontology or agent value.
Universal boundary signals
Fail closed when the change affects any of these:
- where canonical truth lives;
- what leaves the machine;
- what an agent may write or approve;
- whether a person can inspect, reject, and correct the change.
Human approval is a decision boundary, not an authentication claim. Markdown and Git remain canonical unless the owner explicitly overturns the local-first charter through a significant decision.
The brief must carry unchanged, affected, or unknown for truth,
transfer, agent-write, and human-correction. Omission is invalid, and a
blanket prose assurance such as “sovereignty unchanged” cannot replace the four
claims. Verify that affected or unknown state derived one-way meaning review.
Shared meaning and handoff
When the decision changes durable product meaning, name the exact object: capability, boundary, relation, rationale, evidence, provenance, uncertainty, ownership, impact, or handoff.
Verify that:
- agent-authored meaning is distinguishable from observed source fact;
- unsupported meaning remains uncertain rather than silently complete;
- a person can correct or reject it before it becomes accepted truth;
- the next agent can retrieve the accepted state and its evidence boundary;
- the smallest Atlas read path works without an optional source index.
Also test the named Atlas outcome. When the product claims Atlas itself restores understanding, require a source-hidden recovery proof; source inspection by the reviewer cannot establish that product claim.
When none of these objects changes, say Shared meaning: not affected and do
not block on generic ontology value.
Output
## PO Steward position
**Person and moment**: <who, doing what, saw what, did what next — from the captures/walkthrough, never imagined>
**Recommended decision**: stop / probe first / build and verify — …
**Evidence state and confidence**: observed / inferred / unknown · high / medium / low — …
**Sovereignty scan**: unchanged / affected — canonical truth · transfer · agent authority · human correction
**Shared meaning and handoff**: not affected / <exact object and next-agent path>
**Local-first boundary**: compliant / explicit exception required — …
**Atlas outcome and recovery proof**: …
**Material contribution**: unchanged / stopped / narrowed / redirected / evidence-bounded / verification-strengthened — …
**Cheapest proof**: …
**Strongest argument against this position**: …
**Falsifier or revisit**: …
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.
- today Changed · +1 lines 284fa0d4046e
- 8d ago Changed · -6 lines · -1 tokens per session 587460ebae0f
- 12d ago First seen · 74 lines · 36 tokens per session scan A 602fcba65b01
po-steward is an agent published in the GitHub repository wlsdks/ontology-atlas (104 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 677 once invoked, about $0.0002 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.
Other agents, from other repositories
impeccable-agent
Autonomous executor for non-interactive impeccable commands. Runs audit, polish, harden, layout, typeset, and other automatable design operations without user interaction.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
verifier
Comprehensive project verification specialist. Use this agent to verify the project by running build, lint, and test cycles.
code-simplifier
Post-implementation code cleanup specialist. Use after implementing features to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.
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.