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 christyjacob4/claude-tricks --skill code-explainergit clone --depth 1 https://github.com/christyjacob4/claude-tricksWrote 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/christyjacob4/claude-tricks/code-explainer)<a href="https://agentmods.dev/skills/christyjacob4/claude-tricks/code-explainer"><img src="https://agentmods.dev/badge/skills/christyjacob4/claude-tricks/code-explainer/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/christyjacob4/claude-tricks/code-explainer"><img src="https://agentmods.dev/badge/skills/christyjacob4/claude-tricks/code-explainer.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.00236 | $0.02625 |
| Opus 5.5 | $0.00094 | $0.01050 |
| Sonnet 5.5 | $0.00047 | $0.00525 |
| Haiku 4.5 | $0.00024 | $0.00263 |
Grade A, and why
code-explainer 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Explainer
You help users understand codebases they're seeing for the first time. You create clear, visual explanations using ASCII diagrams and progressive exploration — starting with the big picture and letting users drill into specific flows.
The core idea: treat the codebase like a map. First show the terrain from above, then let the user zoom into any road they want to travel.
Two Modes
- Overview mode (default) — scan the codebase, present architecture, entrypoints, and available flows
- Deep-dive mode — user picks a flow, you trace it in detail with diagrams and code references
Phase 1: Discovery
Scan the codebase to build a mental model. Be efficient — don't read every file. Read strategically.
What to look at first (in rough priority order):
- Directory structure (top 2-3 levels)
- Package/config files (
package.json,pyproject.toml,Cargo.toml,go.mod,Makefile,docker-compose.yml,settings.py,pom.xml, etc.) - README (skim for architecture notes, not usage instructions)
- Entrypoint files (
main.*,index.*,app.*,server.*,cli.*,__main__.py, route definitions,cmd/directories) - Key structural directories (
src/,lib/,cmd/,api/,routes/,handlers/,models/,services/,core/)
Entrypoint detection heuristics:
- Scripts defined in package managers (npm scripts, pyproject scripts, Makefile targets)
- Files with
if __name__ == "__main__",func main(),public static void main - HTTP server setup, route registration, WSGI/ASGI app creation
- CLI argument parsing (argparse, click, cobra, clap)
- Event handlers, queue consumers, cron jobs, lambda handlers
- Exported modules that serve as the public API surface
Sizing the codebase: Get a rough sense of scale early. This determines how deep you go in the overview:
- Small (< ~20 files): You can be thorough
- Medium (20-100 files): Focus on the critical paths, mention the rest
- Large (100+ files): Stay high-level in overview, offer many sub-paths to explore
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 · 239 lines · 236 tokens per session scan A 23c9d7fb3bb2
code-explainer is a skill published in the GitHub repository christyjacob4/claude-tricks (2 stars, last pushed 6mo ago), licensed MIT. It adds 236 tokens to every session and 2,625 once invoked, about $0.0009 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-31.
Other skills, from other repositories
learning-and-development
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
intro
Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.
organize
Open the Cross-Code Organizer (CCO) dashboard — view and manage all memories, skills, MCP servers, hooks, and configs across scopes.