render_pdr_status

render_pdr_status is a skill for Claude Code, Codex from pigsly/AxiomFlow. It costs 22 tokens per session (503 once invoked), scanned A, original, MIT.

A renderer that displays PDR results in a bordered Rich panel. PDR results contain signals, scores, breakdowns, and safety-gate statuses.

In plain words
What is it for?
Use it to read JSON from standard input or a lock file and display the overall signal, alignment scores, and safety checks in a transcript-friendly panel.
Why use it?
It gives observation-only results a consistent terminal layout without adding summaries or interpretations.

Skill for Claude CodeCodex

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 skills/pigsly/axiomflow/render_pdr_status
Any agent
npx skills add pigsly/AxiomFlow --skill render_pdr_status
Clone the repo
git clone --depth 1 https://github.com/pigsly/AxiomFlow

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 render_pdr_status

README.md
[![agentmods](https://agentmods.dev/badge/skills/pigsly/axiomflow/render_pdr_status.svg)](https://agentmods.dev/skills/pigsly/axiomflow/render_pdr_status)
Your own site
<a href="https://agentmods.dev/skills/pigsly/axiomflow/render_pdr_status"><img src="https://agentmods.dev/badge/skills/pigsly/axiomflow/render_pdr_status.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 503 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.00022 $0.00503
Opus 5 $0.00011 $0.00251
Sonnet 5 $0.00004 $0.00101
Haiku 4.5 $0.00002 $0.00050

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

Security

Grade A, and why

render_pdr_status 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 4d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/runner.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.codex/skills/render_pdr_status/SKILL.md · 117 lines

What it actually says

SKILL: render_pdr_status

Purpose

Render PDR result with a required Rich bordered panel output.

This skill is observation-only. No summarization. No interpretation.


Input

  • pdr_result (JSON)
{
  "overall_signal": "Review Suggested",
  "alignment_score": 86,
  "breakdown": {
    "req_spec_alignment": 45,
    "adr_alignment": 27,
    "execution_clarity": 14
  },
  "safety_gates": {
    "required_docs_present": true,
    "references_resolved": true,
    "contract_safety": "Needs Clarification"
  }
}

Execution (YAML)

executor: python_script

entry: runner.py

command:
  - python3
  - runner.py

input:
  type: json
  source: stdin
  fallback: lock.json

modes:
  - rich_panel

env:
  RENDER_MODE: rich_panel

rich_panel is the required default mode and renders a bordered status box with the rich package.


Behavior

  1. Parse PDR result (stdin or lock.json)
  2. Normalize fields
  3. Render output

Layout (rich_panel)

Rich bordered status box:

  • title: AxiomFlow PDR Status
  • boxed key/value layout
  • intended for non-interactive terminals and transcript-friendly output
  • must be used as the standard output layout for this skill

Observations and Summary List are intentionally out of scope for this skill. If a workflow requires them, they must be produced by the upstream PDR layer or another renderer.


Constraints

  • No mutation to PDR source
  • Pure rendering only
  • Deterministic output for same input
  • No summarization layer
  • No interpretation
  • No Observations rendering
  • No Summary List generation
  • rich_panel is mandatory

Notes

This skill belongs to the Observation Layer:

PDR Engine → JSON → Render Skill → UI

It must NOT:

  • infer meaning
  • generate summary
  • render Observations
  • generate Summary List
  • suggest actions
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 117 lines · 22 tokens per session scan A 3db1099c0571

Subscribe to this mod's changes

render_pdr_status is a skill published in the GitHub repository pigsly/AxiomFlow (2 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 503 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-31.

Related

Other skills, from other repositories

fork-tab

Open an exact fork of the active Codex CLI chat in a new terminal tab while leaving the source chat open. Use when the user asks to fork, branch, duplicate, or continue the current Codex conversation in another terminal, including phrases such as “fork this into a new tab” or “open a parallel copy of this chat.”.

theelgreco/codex-fork-tab · 71 tokens

git-workflow

This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…

Galaxy-Dawn/claude-scholar · 64 tokens

daily-paper-generator

Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.

Galaxy-Dawn/claude-scholar · 47 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

codex-autoresearch

Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…

leo-lilinxiao/codex-autoresearch · 80 tokens

refine-plan

Iteratively refine development plans using TDD methodology. Ensures plans are clear, actionable, and include red-green-refactor cycles with proper test coverage.

coder/coder · 34 tokens