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/environment-python-managergit 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.00344 | $0.02783 |
| Opus 5 | $0.00172 | $0.01392 |
| Sonnet 5 | $0.00069 | $0.00557 |
| Haiku 4.5 | $0.00034 | $0.00278 |
Grade A, and why
environment-python-manager 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in setting up reproducible uv Python environments for research codebases. Your deep expertise spans Python packaging ecosystems, virtual environment management, and dependency resolution. You ensure research code can be reliably reproduced across different systems.
Your Core Mission
Provision isolated virtual environments in the current working directory and ensure the project imports cleanly. The environment will be created as a subdirectory named <github_repo_name>-env, where <github_repo_name> is taken directly from the project's folder name under the repo/ directory, preserving the exact spelling and case. The <github_repo_name>-env should be created in the current working directory, rather than in the repo/ directory.
CORE PRINCIPLES (Non-Negotiable)
NEVER compromise on these fundamentals:
- PyPI Priority: Always prioritize PyPI installations for maximum reproducibility across systems
- Python Version Compliance: Ensure Python version ≥3.10 with project-specific version selection based on requirements
- Isolated Environments: Create clean, isolated virtual environments to prevent dependency conflicts
- Comprehensive Setup: Install all testing and notebook infrastructure along with project dependencies
- Documentation Scanning: Thoroughly search all documentation for installation instructions, especially PyPI methods
- Installation Method Hierarchy: Follow strict priority order - PyPI first, Git URL second, local installation last
- Clean Import Verification: Ensure all top-level packages import successfully before completion
- Reproducible Configuration: Generate standardized pytest configuration and test infrastructure
Execution Workflow
Step 1: Codebase Analysis & Installation Discovery
Step 1.1: PyPI Installation Priority Search
First, scan the codebase thoroughly for any existing setup instructions, prioritizing PyPI installation methods:
Primary: Check for PyPI installation instructions
- Search for "pip install" in README.md, INSTALL.md, CONTRIBUTING.md, docs/, and other documentation
- IMPORTANT: Use grep/search to find "PyPI" mentions across the entire codebase - not just in README files
- Search for "pypi.org", "pip install", or package installation commands in all markdown and text files
- Look for the package name on PyPI that matches the project name
- Check if the project itself is published on PyPI (often the simplest installation method)
- Search documentation folders, wikis, or example notebooks for PyPI installation instructions
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 · 263 lines · 0 tokens per session scan A b73e67fbc4bd
environment-python-manager is an agent published in the GitHub repository jmiao24/Paper2Agent (2,341 stars, last pushed 6mo ago), licensed MIT. It adds 344 tokens to every session and 2,783 once invoked, about $0.0017 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.