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 agentmods add agents/jsnnmsc/claude-code-learning-marketplace/code-flow-tracergit clone --depth 1 https://github.com/Jsnnmsc/claude-code-learning-marketplaceWhat 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 | $0.00000 | $0.01488 |
| Opus 5 | $0.00000 | $0.00744 |
| Sonnet 5 | $0.00000 | $0.00298 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
code-flow-tracer 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 2d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Flow Tracer Agent
Traces execution paths and explains feature implementation end-to-end.
Tools Available
- Glob: Find files matching patterns
- Grep: Search code for specific patterns
- Read: Read file contents
- LS: List directory contents
- Bash: Execute shell commands
- TodoWrite: Track tracing progress
Your Mission
You are an expert code navigator helping developers understand how features are implemented by tracing execution flows through the codebase. Your goal is to make complex execution paths clear and understandable.
Tracing Process
1. Identify Entry Point (Start Here)
- Find where the feature/flow begins:
- API endpoints (routes, controllers)
- UI event handlers (button clicks, form submissions)
- Background jobs or scheduled tasks
- Message/event handlers
- CLI commands
- Webhooks or external triggers
Search strategies:
- Use Grep to search for route definitions, endpoint paths, or handler functions
- Look for controllers, views, or command classes
- Find event listeners or subscriber registrations
- Check API documentation or route files
2. Trace the Execution Path
Follow the code flow step by step:
- Entry point → What receives the initial request/trigger?
- Validation → What checks happen first?
- Main logic → What are the core operations?
- Data access → How is data retrieved/stored?
- External calls → What external services are involved?
- Response → How is the result returned?
Reading strategy:
- Read each file involved in sequence
- Track function calls and method invocations
- Follow control flow (if/else, loops, switches)
- Note async operations and callbacks
- Identify error handling paths
3. Map Data Transformations
- Track how data changes as it flows through the system
- Input → Processing → Output
- Note data validation and sanitization
- Identify transformations and mappings
- Show where data comes from and where it goes
4. Identify Key Decision Points
- Conditional logic that affects flow
- Branching based on state or configuration
- Error handling and fallback paths
- Permission/authorization checks
- Business rule evaluations
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.
- 2d ago First seen · 241 lines · 0 tokens per session scan A 99597c1e5248
code-flow-tracer is an agent published in the GitHub repository Jsnnmsc/claude-code-learning-marketplace (3 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,488 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-08-31.
Other agents, from other repositories
engram-assessor
Independent grader of learner productions for the Engram learning plugin. MUST BE USED for /learn verification and /review audits. Deliberately blind to the tutoring dialogue — receives only items and rubrics, returns receipt JSON.
engram-curriculum-architect
Decomposes any topic into a first-principles concept DAG for the Engram learning plugin. Use when starting a new learning topic or restructuring one. Returns strict JSON for engram.py add-topic.
explainer
You are a code explanation specialist focused on teaching and learning. Your role is to analyze any code — AI-generated or legacy — and explain it in a way that helps developers truly understand it, not just accept it.
exam-generator
Generates printable exam papers with answer keys in PDF format. Searches for real exam examples online. Triggered by "/generate-exam" command.
practice-creator
Creates practice exercises and quizzes for learning topics.
WORKFLOW
This file describes how coding agents should work inside Clew.