phx-brief

phx-brief is a skill for Claude Code from oliver-kriska/claude-elixir-phoenix. It costs 32 tokens per session (1,151 once invoked), scanned B, a copy of brief, MIT.

An interactive guide to an Elixir or Phoenix implementation plan. It explains the plan's reasoning, data-structure decisions, and component choices in a short walkthrough.

In plain words
What is it for?
Use it to review a new plan or understand work that has already been completed, including its supporting decisions and artifacts.
Why use it?
It helps developers understand why a plan is shaped a certain way before they approve or implement it.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents; names the AskUserQuestion tool.

Good fit Use it to review a new plan or understand work that has already been completed, including its supporting decisions and artifacts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oliver-kriska/claude-elixir-phoenix/phx-brief
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.

Any agent
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-brief
Clone the repo
git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix

Made for: Claude Code.

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 phx-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-brief/github.svg)](https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/phx-brief)
Your own site
<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/phx-brief"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-brief/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 phx-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/phx-brief"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,151 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod 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.01151
Opus 5 $0.00016 $0.00575
Sonnet 5 $0.00006 $0.00230
Haiku 4.5 $0.00003 $0.00115

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

Security

Grade B, and why

phx-brief scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Use Glob to find `.claude/plans/*/plan.md` and pick the most recent.
Origin

This is a copy

86% identical to brief — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

targets/amp/skills/phx-brief/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan Briefing

Interactive walkthrough of a plan's reasoning, decisions, and solution shape. Designed for developers who need to understand a plan in 1-2 minutes instead of reading the full document.

Why This Exists

Plans answer "what to do" but bury "why." This skill bridges that gap with an interactive walkthrough.

Usage

phx-brief                                    # Latest plan
phx-brief .claude/plans/user-auth/plan.md    # Specific plan

Arguments

  • $ARGUMENTS = Path to plan file (optional, auto-detects latest)

Mode Detection

Read the plan file and determine mode from phase statuses:

  • All phases [PENDING] = Pre-work briefing (what WILL happen)
  • Any phase [COMPLETED] or [IN_PROGRESS] = Post-work briefing (what WAS done and why)

Execution Flow

Step 1: Locate and Load Plan

  1. If $ARGUMENTS has a path, use it

  2. Otherwise, find latest plan:

    Use Glob to find .claude/plans/*/plan.md and pick the most recent.

  3. If no plan found, tell user and suggest phx-plan

  4. Read the plan file

Step 2: Load Supporting Artifacts

Read what's available (don't fail if missing):

  • .claude/plans/{slug}/summaries/consolidated.md (research summary)
  • .claude/plans/{slug}/scratchpad.md (decisions, dead-ends)
  • .claude/plans/{slug}/progress.md (work log, post-work only)

Step 3: Present Briefing Sections

Present ONE section at a time, wrapped in the visual briefing block (see references/briefing-guide.md Visual Formatting).

The section MUST be emitted as visible response text BEFORE the AskUserQuestion call. Content composed only in thinking/reasoning is invisible to the user, and the question field is too short to carry it. If the user would see only a "Continue?" dialog, the section was never shown. Write the ★ Briefing block as normal output first, then ask:

  • If sections remain: question "Continue the briefing?" with options "Next: {title}", "Ask me a question about this", "Stop here"
  • If final section: no question needed, show closing message

Read the full file on GitHub · 147 lines

Files

What ships with it

2 files 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. 6d ago First seen · 147 lines · 32 tokens per session scan B c7e648e8c988

Subscribe to this mod's changes

phx-brief is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (542 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 1,151 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 86% identical to brief, differing in 27 lines, and is treated as a copy.

Related

Other skills, from other repositories

teach

Teach the user a new skill or concept, within this workspace.

codingSamss/all-my-ai-needs · 15 tokens

teach

Teach the user a new skill or concept, within this workspace.

saitarrun/Sdlc-ai-workflow · 15 tokens

learning-and-development

Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.

cbrock84/headcount · 64 tokens

vertical-real-estate

Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…

avelikiy/great_cto · 99 tokens

craftcms

Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…

michtio/craftcms-claude-skills · 327 tokens

craft-php-guidelines

Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers…

michtio/craftcms-claude-skills · 336 tokens