Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Dqz00116/skill-libnpx agentmods add skills/dqz00116/skill-lib/paper-first-principlesWrote 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/dqz00116/skill-lib/paper-first-principles)<a href="https://agentmods.dev/skills/dqz00116/skill-lib/paper-first-principles"><img src="https://agentmods.dev/badge/skills/dqz00116/skill-lib/paper-first-principles.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.00027 | $0.00932 |
| Opus 5 | $0.00014 | $0.00466 |
| Sonnet 5 | $0.00005 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
paper-first-principles 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper First Principles
Overview
Convert academic papers into progressive, engineer-friendly documentation using first principles thinking.
When to Use
Use when:
- You need to understand a research paper deeply from an engineering perspective
- Extracting design patterns, system architectures, or algorithms from academic literature
- Preparing technical knowledge sharing or documentation for engineering teams
- Mapping theoretical research to practical software engineering applications
Don't use for:
- Papers without clear technical contributions (survey papers, opinion pieces)
- One-off reading without need for structured documentation
- Standard practices already well-documented elsewhere
Quick Start
# Basic usage
kimi paper-first-principles https://arxiv.org/abs/xxxx.xxxxx
# Engineer perspective with domain focus
kimi paper-first-principles paper.pdf --audience engineer --domain distributed-systems
# Output to file
kimi paper-first-principles paper.pdf --output ./docs/analysis.md
Output Structure
Generated documents contain 8 standard sections:
| Section | Content | Audience |
|---|---|---|
| Opening | One-sentence core insight | All |
| Mechanism Breakdown | Comparative analysis tables | Engineers, Researchers |
| First Principles | Problem essence and design rationale | All |
| Progressive Deep Dive | Layered complexity (simple → complex) | Engineers, Researchers |
| Edge Cases | Common pitfalls and misconceptions | Engineers |
| Decision Tree | When/how to apply | Engineers, Managers |
| Engineering Checklist | Actionable verification items | Engineers |
| Summary | Reusable design patterns | All |
Paper Types & Progressive Paths
| Type | Characteristics | Progressive Path |
|---|---|---|
| Algorithm | New algorithms/models | Example → Core mechanism → Optimizations |
| System | Architecture/engineering | Single-node → Distributed → Production |
| Theory | Theoretical analysis | Problem → Theorem → Proof → Application |
What ships with it
8 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.
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.
- 8d ago First seen · 117 lines · 27 tokens per session scan A 6f6912b00e88
paper-first-principles is a skill published in the GitHub repository Dqz00116/skill-lib (22 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 932 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
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.
tweetclaw
OpenClaw guide for Twitter search, follower exports, monitoring, media, and approved X automation through Xquik. Not affiliated with X Corp.
rosclaw-embodied
A set of rules for completing robot tasks in ROSClaw, a system for running and checking robot work. It covers approved robot files, acceptance evidence, and separate rules for simulation and real hardware.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.
growth-ideas
Describe your product or project and get three actionable growth ideas tailored to your stage.