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/athola/claude-night-marketWrote 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/commands/athola/claude-night-market/visualize)<a href="https://agentmods.dev/commands/athola/claude-night-market/visualize"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/visualize/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/commands/athola/claude-night-market/visualize"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/visualize.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.00016 | $0.00479 |
| Opus 5 | $0.00008 | $0.00239 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
visualize 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 6d 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.
What it actually says
Visualize Codebase
Generate visual diagrams of codebase structure using Mermaid Chart MCP rendering.
Arguments
type- Diagram type:architecture,data-flow,dependency,workflow, orclass(required)scope- Directory path to limit analysis (optional, defaults to project root)
Usage
/visualize architecture
/visualize data-flow plugins/sanctum
/visualize dependency --depth 2
/visualize workflow .github/workflows
/visualize class plugins/sanctum/scripts
Diagram Types
| Type | Skill | Mermaid Format |
|---|---|---|
architecture |
cartograph:architecture-diagram |
flowchart TD |
data-flow |
cartograph:data-flow |
sequenceDiagram |
dependency |
cartograph:dependency-graph |
flowchart LR |
workflow |
cartograph:workflow-diagram |
flowchart TD/LR |
class |
cartograph:class-diagram |
classDiagram |
call-chain |
cartograph:call-chain |
flowchart TD |
communities |
cartograph:code-communities |
flowchart TD |
Workflow
- Parse the diagram type from arguments
- Invoke the matching skill:
architectureinvokesSkill(cartograph:architecture-diagram)data-flowinvokesSkill(cartograph:data-flow)dependencyinvokesSkill(cartograph:dependency-graph)workflowinvokesSkill(cartograph:workflow-diagram)classinvokesSkill(cartograph:class-diagram)call-chaininvokesSkill(cartograph:call-chain)communitiesinvokesSkill(cartograph:code-communities)
- Pass scope argument to the skill
- Skill handles exploration, Mermaid generation, and MCP rendering
Error Handling
If no type argument is provided, display this help text. If an invalid type is provided, show the valid options table above.
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.
- 6d ago First seen · 64 lines · 16 tokens per session scan A 3f3e562ce1e2
visualize is a command published in the GitHub repository athola/claude-night-market (336 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 479 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-09-03.
Other commands, from other repositories
claudex
Claude writes, Codex reviews, iterate until both agree — then ship with love.
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
stats
Agreement stats — how often do Claude and Codex actually agree in this repo?
diff-review
AI-powered diff review for Solana-specific issues and code quality.
demo
A two-minute guided duet — plants bugs in a throwaway repo and lets Claude and Codex argue about them.
pr-issue-resolve
Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.