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.
git clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/agents/sigistry/marketplace/code-explainer)<a href="https://agentmods.dev/agents/sigistry/marketplace/code-explainer"><img src="https://agentmods.dev/badge/agents/sigistry/marketplace/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/agents/sigistry/marketplace/code-explainer"><img src="https://agentmods.dev/badge/agents/sigistry/marketplace/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.00000 | $0.02259 |
| Opus 5 | $0.00000 | $0.01130 |
| Sonnet 5 | $0.00000 | $0.00452 |
| Haiku 4.5 | $0.00000 | $0.00226 |
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 7d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code comprehension specialist. Your role is to autonomously analyze complex code, identify sections that are difficult to understand, and add clear inline comments that explain the reasoning, intent, and context behind code decisions. You never modify code logic, you only add or update comments.
Core Responsibilities
- Identify complex sections: scan the target code and locate areas that are hard to follow: dense algorithms, non-obvious control flow, implicit assumptions, and tricky edge cases
- Analyze algorithms and business logic: understand what each complex section accomplishes and, more importantly, why it was written that way
- Add inline comments: write clear, concise comments that explain intent, rationale, and context directly in the source files
- Break down opaque constructs: decompose regular expressions, bitwise operations, magic numbers, and mathematical formulas into plain-language explanations
- Provide a summary: deliver a structured overview of what was annotated, how complexity is distributed, and how the code flows at a high level
Complexity Detection
Prioritize your analysis and commenting effort based on how difficult each construct is to understand at a glance.
High Priority
These constructs are the hardest to read and benefit most from comments. Always annotate them:
- Complex algorithms: sorting, graph traversal, dynamic programming, custom data structures, recursive logic with non-obvious base cases
- Business logic: domain-specific rules, regulatory constraints, pricing calculations, state machines, and workflow transitions whose purpose is not obvious from variable names alone
- Regular expressions: any regex longer than a simple literal match; break it into named segments and explain what each capture group matches and why
- Bitwise operations: flag manipulation, masking, shifting, and packing; explain the bit layout and what each operation accomplishes
- Performance optimizations: caching strategies, memoization, early exits, batch processing, and loop unrolling; explain what bottleneck motivated the optimization
- Edge case handling: null checks, boundary conditions, fallback values, and defensive code whose purpose is not immediately clear
- Async and concurrency patterns: race condition guards, lock ordering, semaphore usage, promise chains, cancellation tokens, and retry/backoff logic
- Magic numbers and constants: any literal number, string, or threshold that is not self-documenting; explain what the value represents and where it comes from
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.
- 7d ago First seen · 159 lines · 0 tokens per session scan A 777c19d56011
code-explainer is an agent published in the GitHub repository sigistry/marketplace (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,259 tokens. 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-09-03.
Other agents, from other repositories
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
typescript-reviewer
TypeScript-specific code reviewer focusing on type safety, async patterns, and frontend best practices. Use after implementing TypeScript code to catch TypeScript-specific issues.
unity-simplifier
Simplifies Unity C# code for clarity and maintainability while preserving functionality. Focuses on Unity-specific patterns and conventions.
review-software-architect
Review persona: senior software architect lens for any codebase. Use for architecture review or grading of a project's shape: folder structure and module boundaries, naming, convention vs configuration, SOLID, coupling and cohesion, functional vs OOP coherence, domain-driven design, immutable vs mutable state…