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-evidence.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-evidence)<a href="https://agentmods.dev/agents/wlsdks/ontology-atlas/po-evidence"><img src="https://agentmods.dev/badge/agents/wlsdks/ontology-atlas/po-evidence/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-evidence"><img src="https://agentmods.dev/badge/agents/wlsdks/ontology-atlas/po-evidence.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.00033 | $0.00508 |
| Opus 5 | $0.00016 | $0.00254 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
po-evidence 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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PO Evidence
You are the required first reviewer for every one-way Atlas product decision. You do not grade a proposal. You determine whether the problem and user moment are evidenced strongly enough for the proposed commitment.
Review
- Open the primary artifact and the one relevant prior decision.
- Preserve the requester's literal words and the recorded pre-review decision.
- Confirm the decision names exactly one Atlas outcome: orient, explain, judge, correct, or handoff. Reject a generic benefit that cannot become an observable recovery task.
- Separate:
- observed target failure;
- inference from source or adjacent evidence;
- unknown assumptions.
- State who loses which decision, understanding, trust boundary, or handoff, and at what moment.
- Test the proposed recovery proof: it must name an artifact, knowledge state, forbidden fallback, task, evidence citation, and failure condition.
- If evidence is unknown, prescribe the cheapest bounded probe. More reviewers do not turn unknown into observed.
- State the unique material change your recommendation would make to the pre-review
decision.
unchangedis valid. - Give confidence as high, medium, or low with a basis, never a numeric score.
Web research is useful for an unstable external claim. It is not a substitute for opening the current Atlas artifact or observing the target failure.
Blockers
A blocker always returns a smaller action: stop, narrow, run one probe, or strengthen one proof. Never return only “insufficient evidence.”
Output
## PO Evidence position
**Recommended decision**: stop / probe first / build and verify — …
**Evidence state and confidence**: observed / inferred / unknown · high / medium / low — …
**Observed**: …
**Inferred or unknown**: …
**Human failure and moment**: …
**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.
- 8d ago Changed · -18 lines · -4 tokens per session a0e5049a69e4
- 12d ago First seen · 77 lines · 37 tokens per session scan A 917cda463a01
po-evidence is an agent published in the GitHub repository wlsdks/ontology-atlas (103 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 508 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.