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.
npx agentmods add skills/stefan-jansen/claude-code-toolkit/pyramid-principlenpx skills add stefan-jansen/claude-code-toolkit --skill pyramid-principlegit clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitWrote 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/skills/stefan-jansen/claude-code-toolkit/pyramid-principle)<a href="https://agentmods.dev/skills/stefan-jansen/claude-code-toolkit/pyramid-principle"><img src="https://agentmods.dev/badge/skills/stefan-jansen/claude-code-toolkit/pyramid-principle.svg" alt="Measured on agentmods" 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.00020 | $0.02275 |
| Opus 5 | $0.00010 | $0.01137 |
| Sonnet 5 | $0.00004 | $0.00455 |
| Haiku 4.5 | $0.00002 | $0.00228 |
Grade A, and why
pyramid-principle 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.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pyramid Principle Skill
Foundation: Barbara Minto's pyramid principle for clear, logical communication
Core Concept: Start with the answer, then provide supporting arguments, then add details.
Why This Works:
- Reader gets main point immediately (respects their time)
- Supporting structure makes logical sense
- Details are contextualized (not lost)
- Reader can stop at any level and still understand core idea
- Reduces cognitive load (top-down, not bottom-up)
The Pyramid Structure
[ANSWER / Core Message]
|
┌──────────────────┼──────────────────┐
| | |
[Argument 1] [Argument 2] [Argument 3]
| | |
┌───┼───┐ ┌───┼───┐ ┌───┼───┐
| | | | | | | | |
[Details] [Details] [Details] [Details] [Details] [Details]
Levels:
- Level 1: The answer/conclusion (what they need to know)
- Level 2: Major supporting arguments (why answer is true)
- Level 3: Evidence and examples (what proves arguments)
- Level 4: Details and elaboration (depth as needed)
Core Rules
Rule 1: Answer First
Always start with the conclusion
❌ Don't do this (bottom-up):
We analyzed 10 frameworks. We tested each for 6 months.
We measured productivity, reliability, and ease of use.
Framework X performed best. Therefore, we recommend Framework X.
✅ Do this (top-down):
**We recommend Framework X** because it delivers 30% higher productivity
with proven reliability over 6 months of testing.
Here's why:
1. Productivity: 30% improvement vs alternatives
2. Reliability: Zero critical failures in production
3. Ease of adoption: 2-week learning curve vs 2-month for alternatives
Why: Reader knows the answer immediately. Supporting details provide confidence, but aren't prerequisite to understanding recommendation.
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.
- 6d ago First seen · 334 lines · 20 tokens per session scan A 1dc0bdd5d269
pyramid-principle is a skill published in the GitHub repository stefan-jansen/claude-code-toolkit (86 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 2,275 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-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
ax-agent-rlm
This skill helps an LLM generate correct AxAgent RLM/runtime code using @ax-llm/ax. Use when the user asks about RLM code execution, AxJSRuntime, contextFields, contextPolicy, liveRuntimeState, promptLevel, stage prompt controls, executorModelPolicy, maxRuntimeChars, agent.test(...), llmQuery(...), recursionOptions…