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/sigistry/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/sigistry/marketplace/code-tutor)<a href="https://agentmods.dev/plugins/sigistry/marketplace/code-tutor"><img src="https://agentmods.dev/badge/plugins/sigistry/marketplace/code-tutor/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/plugins/sigistry/marketplace/code-tutor"><img src="https://agentmods.dev/badge/plugins/sigistry/marketplace/code-tutor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-tutor 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 1mo 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": "code-tutor",
"version": "1.0.0",
"description": "AI-powered code learning and mentoring system with interactive teaching, code explanations, practice exercises, and educational code reviews",
"author": {
"name": "Sigistry Code Tutor",
"url": "https://github.com/Sigistry/marketplace/tree/main/plugins/code-tutor"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 4 commands travel with it, and installing the plugin installs all of them — 107 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.
- 1mo ago First seen · 11 lines scan A 830897258fa7
code-tutor is a plugin published in the GitHub repository sigistry/marketplace (3 stars, last pushed yesterday), 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
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
review
PR review, interactive git diff annotation review, and writing style guide.
handbook-code-review
Code review plugin with a standalone reviewer agent and two skill strategies: disposable subagents for one-shot reviews and persistent team members for iterative reviews.
adv
Adversarial multi-model code review and model dispatch. Orchestrates Claude, Codex CLI, and Gemini CLI for cross-examined code review with 5 specialized reviewers.
learning-guide
Generate a single-file, interactive HTML learning guide for any artifact — codebase, planning session, refactor plan, or generic input — via an analyze → render flow with a JSON tour-spec contract.
review-pr
Review PRs in a Tour Guide (expository) or Adversarial (audit) posture, with logical file ordering, context, and severity-rated findings. Forge-agnostic (GitHub + Bitbucket).