tldr-router — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited tldr-router (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Maps questions to the optimal tldr command. Use this to pick the right layer.
tldr tree . --ext .py # File overview
tldr structure src/ --lang python # Function/class overviewUse: Starting exploration, orientation
tldr context <function> --project . --depth 2
tldr calls src/Use: Understanding architecture, finding entry points
tldr cfg <file> <function>Use: Identifying refactoring candidates, understanding difficulty
tldr dfg <file> <function>Use: Debugging, understanding data flow
tldr slice <file> <function> <line>Use: Impact analysis, safe refactoring
tldr search "pattern" src/Use: Finding code, structural search
START
│
├─► "What exists?" ──► tree / structure
│
├─► "How does X connect?" ──► context / calls
│
├─► "Why is X complex?" ──► cfg
│
├─► "Where does Y flow?" ──► dfg
│
├─► "What depends on Z?" ──► slice
│
└─► "Find something" ──► search| Intent | Keywords | Layer |
|---|---|---|
| Navigation | "what", "where", "find", "exists" | tree, structure, search |
| Architecture | "calls", "uses", "connects", "depends" | context, calls |
| Complexity | "complex", "refactor", "branches", "paths" | cfg |
| Data Flow | "variable", "value", "assigned", "comes from" | dfg |
| Impact | "affects", "changes", "slice", "dependencies" | slice/pdg |
| Debug | "bug", "error", "investigate", "broken" | cfg + dfg + context |
The tldr-read-enforcer and tldr-context-inject hooks automatically:
You don't need to manually run these commands - the hooks do it for you.
If you need a specific layer the hooks didn't provide:
# Force specific analysis
tldr cfg path/to/file.py function_name
tldr dfg path/to/file.py function_name
tldr slice path/to/file.py function_name 42~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.