problem-first-explanation

problem-first-explanation is a skill for Claude Code, Codex from fabiandistler/agents. It costs 51 tokens per session (870 once invoked), scanned A, original, no licence file.

A writing rule for technical explanations that starts with the concrete problem before describing the abstract idea or implementation.

In plain words
What is it for?
It is for writing clearer documentation, READMEs, tutorials, architecture decision records, and explanations of technical concepts.
Why use it?
It makes unfamiliar concepts easier to understand by showing their purpose before introducing how they work.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit It is for writing clearer documentation, READMEs, tutorials, architecture decision records, and explanations of technical concepts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fabiandistler/agents/problem-first-explanation
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 fabiandistler/agents --skill problem-first-explanation
Clone the repo
git clone --depth 1 https://github.com/fabiandistler/agents

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 problem-first-explanation

README.md
[![agentmods](https://agentmods.dev/badge/skills/fabiandistler/agents/problem-first-explanation.svg)](https://agentmods.dev/skills/fabiandistler/agents/problem-first-explanation)
Your own site
<a href="https://agentmods.dev/skills/fabiandistler/agents/problem-first-explanation"><img src="https://agentmods.dev/badge/skills/fabiandistler/agents/problem-first-explanation.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 870 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 unknown 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.00051 $0.00870
Opus 5 $0.00026 $0.00435
Sonnet 5 $0.00010 $0.00174
Haiku 4.5 $0.00005 $0.00087

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

Security

Grade A, and why

problem-first-explanation 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 7d 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.

skills/problem-first-explanation/SKILL.md · 63 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 7d ago First seen · 63 lines · 51 tokens per session scan A 189b82d51b40

Subscribe to this mod's changes

problem-first-explanation is a skill published in the GitHub repository fabiandistler/agents (2 stars, last pushed yesterday), with no licence file. It adds 51 tokens to every session and 870 once invoked, about $0.0003 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

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

one-three-one-rule

1-3-1 decision briefs: problem, three options, one pick.

NousResearch/hermes-agent · 21 tokens

simplified-english

Write user-facing comments, plans, and documents in ASD-STE100 Simplified Technical English — short, unambiguous sentences with approved words and one meaning each — so readers understand them the first time.

paperclipai/paperclip · 46 tokens

response-compression

Compresses verbose responses by removing filler and framing to save 200-400 tokens. Use when responses feel bloated or context is filling fast.

athola/claude-night-market · 33 tokens

novu-inbox-integration

Integrate Novu's in-app notification inbox into web applications. Supports React, Next.js, and vanilla JavaScript. Includes the Inbox component (bell icon + notification feed), composable components (Bell, Notifications, InboxContent, Preferences), headless hooks, branded theming, custom render props, multi-tenancy…

novuhq/novu · 111 tokens

novu-design-workflow

Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…

novuhq/novu · 114 tokens