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/catfish-1234/proctorWrote 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/catfish-1234/proctor/gemini-extension)<a href="https://agentmods.dev/plugins/catfish-1234/proctor/gemini-extension"><img src="https://agentmods.dev/badge/plugins/catfish-1234/proctor/gemini-extension/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/catfish-1234/proctor/gemini-extension"><img src="https://agentmods.dev/badge/plugins/catfish-1234/proctor/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
proctor 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 yesterday.
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": "proctor",
"version": "1.0.0",
"description": "Catches AI coding agents gaming their test suites: deleting tests, skipping them, weakening assertions, or hardcoding outputs to fake a green build.",
"contextFileName": "PROCTOR.md"
}
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.
- yesterday First seen · 7 lines scan A 1bd91772f021
proctor is a plugin published in the GitHub repository catfish-1234/proctor (1 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-09-10.
Other plugins, from other repositories
superstack
An agent-based software-development system that guides work from a short request to a tested, demonstrated piece of software. It uses checkpoints for planning and verification and explains conclusions in plain language.
dev-loop
loop-orchestrator's verification loop (TDD / PDCA / Reflexion) with the plan step FIXED to a wiki-grounded planning methodology (wiki-plan): every design decision is routed to a bundled semantic-layer wiki before code is written. Adds a knowledge-capture loop — sessions emit verified insights, and knowledge-flush…
beast-forge
Plan iron, verify real. Ironclad planning with independent verification chain. Turns any input into a bulletproof plan, executes with TDD, verifies with independent agents.
posthog
Access PostHog analytics, feature flags, experiments, error tracking, and insights directly from your AI coding tool. Optionally capture Claude Code sessions to PostHog LLM Analytics.
e2e-dashboard
Install a real-time Playwright E2E test dashboard (live SSE progress, 14 features) into any project.
mobile-app-testing
Test your web app on real iOS Simulator / Android emulator sessions via tapflow, alongside your existing Playwright suite.