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 skills add notlate-cn/code-reader-skills --skill code-reader-engit clone --depth 1 https://github.com/notlate-cn/code-reader-skillsWrote 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/notlate-cn/code-reader-skills/code-reader-en)<a href="https://agentmods.dev/skills/notlate-cn/code-reader-skills/code-reader-en"><img src="https://agentmods.dev/badge/skills/notlate-cn/code-reader-skills/code-reader-en/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.
<a href="https://agentmods.dev/skills/notlate-cn/code-reader-skills/code-reader-en"><img src="https://agentmods.dev/badge/skills/notlate-cn/code-reader-skills/code-reader-en.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.06542 |
| Opus 5.5 | $0.00028 | $0.02617 |
| Sonnet 5.5 | $0.00014 | $0.01308 |
| Haiku 4.5 | $0.00007 | $0.00654 |
Grade A, and why
code-reader-v2-en 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 1mo 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 — 723 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Code Deep Understanding Analyzer v2.3 (English Version)
Professional code analysis tool based on cognitive science research, supporting three analysis depths to ensure true understanding rather than fluency illusion.
Core Principle: Understand WHY, not just WHAT. Explain like an experienced engineer talking to a friend, not a textbook stacking jargon.
Research Foundation: Dunlosky et al. · Chi et al. · Karpicke & Roediger
Three Analysis Modes
| User Intent | Mode | Trigger Examples | Duration |
|---|---|---|---|
| Quick browse / code review | Quick | "quick look", "what does this do", "briefly scan" | 5-10 min |
| Learning / technical research | Standard ⭐ | "analyze", "help me understand", "explain", "what's the principle" | 15-20 min |
| Deep mastery / large projects | Deep 🚀 | "thoroughly analyze", "completely master", "deep dive", "interview prep", "full project analysis" | 30+ min |
Default: Standard Mode. System auto-selects mode based on code scale and user intent.
Deep Mode internal strategy selection:
if lines_of_code <= 2000:
Strategy A: Progressive generation (sequential chapter filling)
elif lines_of_code <= 10000 and file_count <= 20:
Strategy B: Parallel processing (sub-agent chapter-level parallel)
else: # lines > 10000 or files > 20
Strategy C: Layered parallel (module-level scan → chapter-level parallel)
Analysis Output Structure
Quick Mode (5-10 min)
# [Code Name] Quick Analysis
## 1. Quick Overview
- Programming language and version / Code scale and type / Core dependencies
## 2. Functionality Description
- Main functionality (WHAT) + brief WHY
## 3. Core Algorithm/Design
- Complexity (if applicable) + Design patterns (if applicable) + WHY chosen
## 4. Key Code Segments
- 3-5 core code segments, brief description of each
## 5. Dependencies
- External library list and purposes
## 6. Quick Usage Example
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.
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.
- 1mo ago First seen · 723 lines · 0 tokens per session scan A 71b0c8cb055b
code-reader-v2-en is a skill published in the GitHub repository notlate-cn/code-reader-skills (176 stars, last pushed 6mo ago), licensed MIT. It adds 70 tokens to every session and 6,542 once invoked, about $0.0003 per session on Opus 5.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
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
eli5
Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works, and every schema change.
review-animations
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
ship-feature
End-to-end feature delivery — implement a feature, verify builds/tests pass, open a fully-filled draft PR, then automatically push every feedback round and review iteration to the same PR. Use when the user asks to implement or build a feature, fix-and-ship a change, or iterate on an existing feature PR.