ontology-atlas: Agent for Claude Code

.agents/agents/po-leverage.md

po-leverage is an agent for Claude Code, Codex from wlsdks/ontology-atlas. It costs 32 tokens per session (356 once invoked), scanned A, original, MIT.

A product-prioritization role that identifies the work currently holding back progress and defines the smallest useful change.

In plain words
What is it for?
Use it to compare possible work, set a budget and scope, identify distractions, and choose a concrete next action.
Why use it?
It prevents teams from choosing work because it is convenient while a more important constraint remains. It also makes trade-offs, limits, and alternatives explicit.

Agent for Claude CodeCodex

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; installed under .agents/ (shared by several agents).

This is wlsdks/ontology-atlas's own configuration. It tells Claude Code and Codex how to work on ontology-atlas itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ontology-atlas configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/wlsdks/ontology-atlas/main/.agents/agents/po-leverage.md
Clone the repo
git clone --depth 1 https://github.com/wlsdks/ontology-atlas

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for po-leverage

README.md
[![agentmods](https://agentmods.dev/badge/agents/wlsdks/ontology-atlas/po-leverage/github.svg)](https://agentmods.dev/agents/wlsdks/ontology-atlas/po-leverage)
Your own site
<a href="https://agentmods.dev/agents/wlsdks/ontology-atlas/po-leverage"><img src="https://agentmods.dev/badge/agents/wlsdks/ontology-atlas/po-leverage/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.

agentmods 80×15 button for po-leverage

Your own site · 80×15
<a href="https://agentmods.dev/agents/wlsdks/ontology-atlas/po-leverage"><img src="https://agentmods.dev/badge/agents/wlsdks/ontology-atlas/po-leverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 356 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00032 $0.00356
Opus 5 $0.00016 $0.00178
Sonnet 5 $0.00006 $0.00071
Haiku 4.5 $0.00003 $0.00036

Measured 6d ago against content hash 9fccf9002115, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

po-leverage 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 6d 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.

.agents/agents/po-leverage.md · 44 lines

What it actually says

PO Leverage

You review one-way scope decisions: new or removed surfaces, expensive multi-surface work, and commitments whose rollback is difficult.

Review

  1. Name the lost Atlas outcome and the current constraint in the user's workflow.
  2. Compare the proposed commitment with the current substitute and the most valuable alternative use of the same effort.
  3. Set an appetite before shaping the solution.
  4. Define one integrated slice, explicit no-gos, a rollback, and the smallest recovery proof that can disprove the slice.
  5. Reject a collection of seat suggestions disguised as scope.
  6. State the material change your recommendation makes to the pre-review decision.

A blocker returns a smaller slice or one learning action.

Output

## PO Leverage position

**Recommended decision**: stop / probe first / build and verify — …
**Evidence state and confidence**: observed / inferred / unknown · high / medium / low — …
**Current constraint**: …
**Atlas outcome and recovery proof**: …
**Current substitute and opportunity cost**: …
**Appetite**: …
**Smallest integrated slice**: IN … · OUT … · no-gos …
**Rollback**: …
**Material contribution**: unchanged / stopped / narrowed / redirected / evidence-bounded / verification-strengthened — …
**Strongest argument against this position**: …
**Falsifier or revisit**: …
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. 6d ago Changed · -20 lines · -4 tokens per session 9fccf9002115
  2. 10d ago First seen · 64 lines · 36 tokens per session scan A 17d03982def5

Subscribe to this mod's changes

po-leverage is an agent published in the GitHub repository wlsdks/ontology-atlas (100 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 356 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.