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.
/plugin marketplace add jkanselaar/python-code-validatornpx agentmods add plugins/jkanselaar/python-code-validator/plugingit clone --depth 1 https://github.com/jkanselaar/python-code-validatorGrade A, and why
python-code-validator 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": "python-code-validator",
"displayName": "Python Code Validator",
"version": "1.0.0",
"description": "Checks every Python file Claude writes, before you read it: syntax, lint, types, an AST security policy and a credential scan, with the exact fix when there is one.",
"author": {
"name": "StateMind",
"url": "https://api.statemind.ai"
},
"homepage": "https://api.statemind.ai",
"repository": "https://github.com/jkanselaar/python-code-validator",
"license": "MIT",
"keywords": ["python", "validation", "security", "lint", "code-quality"],
"hooks": "./hooks/hooks.json"
}
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 · 16 lines scan A 88270c93af9f
python-code-validator is a plugin published in the GitHub repository jkanselaar/python-code-validator (0 stars, last pushed 15d 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
logic-lens-marketplace
Plugin marketplace listing 1 plugin: logic-lens.
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, semantic errors, and runtime failures that linters miss.
horizon-shield
Audit Japanese construction and renovation estimates against the open JCCDB dataset and return Bitcoin-anchored, independently recomputable fair-price receipts. Read-only remote MCP, no API key. Adds /audit, /red-flags, /verify commands.
the-horizons
Plugin marketplace listing 1 plugin: horizon-shield.
score-technologies
Plugin marketplace listing 1 plugin: score-studio.
score-studio
Operate evidence-gated computer-vision workflows in Score Studio.