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/TimboGP/timbogp-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/plugins/timbogp/timbogp-marketplace/agentic-study-environment)<a href="https://agentmods.dev/plugins/timbogp/timbogp-marketplace/agentic-study-environment"><img src="https://agentmods.dev/badge/plugins/timbogp/timbogp-marketplace/agentic-study-environment.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agentic-study-environment 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.
What it actually says
{
"name": "agentic-study-environment",
"version": "0.6.0",
"description": "A Claude Code learning harness: structured tutor sessions over your own source materials, in any domain.",
"author": {
"name": "TimboGP"
},
"homepage": "https://github.com/TimboGP/timbogp-marketplace",
"repository": "https://github.com/TimboGP/timbogp-marketplace",
"license": "MIT",
"keywords": [
"learning",
"tutor",
"education",
"study",
"harness",
"meta-framework",
"domain-overlay"
]
}
What it installs
The manifest is a name and a version. 7 skills, 1 command travel with it, and installing the plugin installs all of them — 1,131 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 21 lines scan A 1f0464c55dc6
agentic-study-environment is a plugin published in the GitHub repository TimboGP/timbogp-marketplace (3 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
gan-zhong-xue
A learning add-on that turns AI-made code changes into guided, explainable understanding. It uses a question-and-answer process so developers can restate the reasoning and apply it elsewhere.
explain
Structured code explainer — layered explanations of files, functions, directories, or concepts.
swarm-skill
Multi-agent codebase audit skill for Claude Code — spawns parallel subagents (security, performance, tests, architecture, dead-code) and synthesizes their findings into a prioritized action plan.
study-mode
Strict tutor mode. Turns Claude into a teacher that paces one concept at a time, verifies understanding, gathers resources, reviews YOUR code, and hard-blocks itself from writing code for you.
shumo-paper
A Chinese-language assistant for the National College Students Mathematical Modeling Competition. It covers problem analysis, model selection, data preparation, solving, result checks, and writing the competition paper.
dev-pipeline
A 5-phase development pipeline (requirement engineering, system architecture, task generation, verified implementation, code review) with an optional QA gate (plan-qa + execute-qa) for changes that have a running surface worth driving — independent of /review, run sequentially or in parallel at the developer's…