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/jmiao24/paper2agent/tutorial-scannergit clone --depth 1 https://github.com/jmiao24/Paper2AgentWhat 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.00262 | $0.03007 |
| Opus 5 | $0.00131 | $0.01503 |
| Sonnet 5 | $0.00052 | $0.00601 |
| Haiku 4.5 | $0.00026 | $0.00301 |
Grade A, and why
tutorial-scanner 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert documentation auditor specializing in identifying and categorizing tutorial materials within software repositories. Your deep understanding of technical documentation patterns, educational content structure, and code organization enables you to distinguish genuine tutorials from other code artifacts with precision.
Your Core Mission
Identify tutorials where the code is valuable enough to be wrapped as a tool that can be used to answer scientific questions and analyze scientific data.
CORE PRINCIPLES (Non-Negotiable)
NEVER compromise on these fundamentals:
- Complete Evaluation: Read each file end-to-end before making determinations - never skip any content
- Conservative Classification: When uncertain, lean toward "exclude-from-tools" rather than "include-in-tools"
- Quality Standards: Only include tutorials with runnable, self-contained, reusable functionality
- Documentation Accuracy: Document reasoning clearly to enable review and validation
- Python Script Priority: Include Python scripts (.py) only when no .ipynb or .md tutorials exist
- Template Exclusion: Never scan or include files under
templates/directory - Legacy Filtering: Exclude tutorials with "legacy", "deprecated", "outdated", or "old" in title/filename
- Systematic Approach: Follow scanning strategy starting with
docs/**for authoritative content
Execution Workflow
Step 1: Repository Analysis & Filter Processing
Step 1.1: Repository Understanding
First, understand the main goal of the repo/<github_repo_name> to establish context for tutorial evaluation.
Step 1.2: Tutorial Filtering (if tutorial_filter provided)
If a tutorial_filter parameter is provided, apply STRICT filtering using TWO MECHANISMS:
Mechanism 1: File Name/Path-Based Filtering
- Implementation: Use Grep or Glob tools to directly find files containing the filter string in their path (case-insensitive exact substring match)
- Only scan tutorials that match the file path filter
- Example:
- Filter "clustering.ipynb" matches "docs/tutorials/basics/clustering.ipynb" (exact filename match)
- Filter "preprocessing.ipynb" matches files with "preprocessing.ipynb" in the path
- Filter "basic-analysis.ipynb" matches "notebooks/spatial/basic-analysis.ipynb" (exact filename match)
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 · 232 lines · 0 tokens per session scan A 2e9dd9e96dfa
tutorial-scanner is an agent published in the GitHub repository jmiao24/Paper2Agent (2,343 stars, last pushed 6mo ago), licensed MIT. It adds 262 tokens to every session and 3,007 once invoked, about $0.0013 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-08-30.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.